Secuno
ENNL
Book demo

CVE-2024-6800

GitHub Enterprise Server vulnerability

9.8 CRITICALEPSS 1.53%
  1. Published20 Aug 2024

Description

An XML signature wrapping vulnerability was present in GitHub Enterprise Server (GHES) when using SAML authentication with specific identity providers utilizing publicly exposed signed federation metadata XML. This vulnerability allowed an attacker with direct network access to GitHub Enterprise Server to forge a SAML response to provision and/or gain access to a user with site administrator privileges. Exploitation of this vulnerability would allow unauthorized access to the instance without requiring prior authentication. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.14 and was fixed in versions 3.13.3, 3.12.8, 3.11.14, and 3.10.16. This vulnerability was reported via the GitHub Bug Bounty program.

CVSS 3.1 breakdown

Attack vectorNetwork
Attack complexityLow
Privileges requiredNone
User interactionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityHigh
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

GitHub Enterprise Server≥ 3.10.0 < 3.10.16 · ≥ 3.11.0 < 3.11.14 · ≥ 3.12.0 < 3.12.8 · ≥ 3.13.0 < 3.13.3

Remediation

Fixed in
GitHub Enterprise Server≥ 3.10.16

Frequently asked

Is CVE-2024-6800 being actively exploited?

CVE-2024-6800 is not in the CISA KEV catalog. Its EPSS exploit probability is 1.53%.

How severe is CVE-2024-6800?

CVE-2024-6800 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 1.53% probability of exploitation.

Which products are affected by CVE-2024-6800?

Affected products include GitHub Enterprise Server.

How do I fix CVE-2024-6800?

Upgrade affected software to a fixed version, for example GitHub Enterprise Server 3.10.16 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2024-6800 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation worksBook a demo

Get Patch this first every Monday

Five vulnerabilities that matter this week, ranked on real exploitation. Plain language, one email, no spam.

You can unsubscribe with one click from every issue. We handle your details as described in our privacy policy.

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.