cve.bz

CVE-2024-9487 github enterprise server

9.5 criticalEPSS 26%Fix available

Critical (9.5) in github enterprise server. EPSS 26% estimated probability of exploitation activity in the next 30 days.

On this page
An improper verification of cryptographic signature vulnerability was identified in GitHub Enterprise Server that allowed SAML SSO authentication to be bypassed resulting in unauthorized provisioning of users and access to the instance. Exploitation required the encrypted assertions feature to be enabled, and the attacker would require direct network access as well as a signed SAML response or metadata document. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.15 and was fixed in versions 3.11.16, 3.12.10, 3.13.5, and 3.14.2. This vulnerability was reported via the GitHub Bug Bounty program.

Severity

CVSS 4.0

9.5 critical
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:L/SC:H/SI:H/SA:L/R:U/V:C/RE:M/U:Red

CVSS 3.1

9.1 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
EPSS
26% (unchanged from 26% a week ago; 26% 30 days ago) estimated probability of exploitation activity in the next 30 days; 98th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2024-10-11. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-347 Improper Verification of Cryptographic Signature
OWASP Top 10
A04:2025 Cryptographic Failures
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

  • GitHub Enterprise Server: fixed in 3.11.16
  • GitHub Enterprise Server: fixed in 3.12.10
  • GitHub Enterprise Server: fixed in 3.13.5
  • GitHub Enterprise Server: fixed in 3.14.2

Ask an AI about this CVE

Show the promptExplain CVE-2024-9487 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2024-9487?via=ask-ai-copy and https://cve.bz/cve/CVE-2024-9487?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2024-9487 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
GitHub Enterprise Serverfrom 3.11.0 through 3.11.15
GitHub Enterprise Serverfrom 3.12.0 through 3.12.9
GitHub Enterprise Serverfrom 3.13.0 through 3.13.4
GitHub Enterprise Serverfrom 3.14.0 through 3.14.1

Fixed in

ProductFixed in
GitHub Enterprise Server3.11.16
GitHub Enterprise Server3.12.10
GitHub Enterprise Server3.13.5
GitHub Enterprise Server3.14.2

Detection rules

Ways to detect this CVE, not exploit code: the nuclei template that checks a system for it, and the Suricata and Snort rules that name it. A rule set may ship a rule turned off, so check yours by its sid.

  • Emerging Threats Open ET WEB_SPECIFIC_APPS Github Enterprise SAML Authentication Bypass (CVE-2024-9487) sid 2061124

Attack patterns (CAPEC)

  • CAPEC-463 Padding Oracle Crypto Attack Severity: High
  • CAPEC-475 Signature Spoofing by Improper Validation Likelihood: Low · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON