Authentication bypass via improper SAML signature verification
Published Oct 10, 2024 · Updated Oct 11, 2024
Authentication bypass in GitHub Enterprise Server allows remote attackers to provision unauthorized users and access an instance via SAML SSO. The SAML authentication flow improperly verifies a cryptographic signature associated with an encrypted assertion, although GitHub has not disclosed the affected code path or exact validation error. Exploitation requires direct network access, enabled encrypted assertions, and a signed SAML response or metadata document.
Summary
What happened
Authentication bypass in GitHub Enterprise Server allows remote attackers to provision unauthorized users and access an instance via SAML SSO. The SAML authentication flow improperly verifies a cryptographic signature associated with an encrypted assertion, although GitHub has not disclosed the affected code path or exact validation error. Exploitation requires direct network access, enabled encrypted assertions, and a signed SAML response or metadata document.
The record
- CVE
- CVE-2024-9487
- Published
- Oct 10, 2024
- Updated
- Oct 11, 2024
- Vendor
- Product
- GitHub Enterprise Server
- Classifications
- CWE-347, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 10, 2024CVE publishedPublication date reported by the CVE source.
- Oct 11, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.11.0 <=3.11.15
- Affected versionversion=3.11.0 <=3.11.15 changes=[{"at":"3.11.16","status":"unaffected"}]
- Affected versionversion=3.12.0 <=3.12.9
- Affected versionversion=3.12.0 <=3.12.9 changes=[{"at":"3.12.10","status":"unaffected"}]
- Affected versionversion=3.13.0 <=3.13.4
- Affected versionversion=3.13.0 <=3.13.4 changes=[{"at":"3.13.5","status":"unaffected"}]
- Affected versionversion=3.14.0 <=3.14.1
- Affected versionversion=3.14.0 <=3.14.1 changes=[{"at":"3.14.2","status":"unaffected"}]
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo