Enterprise ServerApplication · GitHub
CVE-2024-10001
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA Code Injection vulnerability was identified in GitHub Enterprise Server that allowed attackers to inject malicious code into the query selector via the identity property in the message handling function. This enabled the exfiltration of sensitive data by manipulating the DOM, including authentication tokens. To execute the attack, the victim must be logged into GitHub and interact with the attacker controlled malicious webpage containing the hidden iframe. This vulnerability occurs due to an improper sequence of validation, where the origin check occurs after accepting the user-controlled identity property. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.11.16, 3.12.10, 3.13.5, 3.14.2, and 3.15.0. This vulnerability was reported via the GitHub Bug Bounty program.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA code injection vulnerability in GitHub Enterprise Server allows attackers to inject malicious code into the query selector via the identity property in the message handling function. The vulnerability occurs because the origin check happens after accepting the user-controlled identity property, enabling DOM manipulation to exfiltrate sensitive data including authentication tokens.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Enterprise ServerApplication
< 3.11.6>= 3.12.0, < 3.12.10>= 3.13.0, < 3.13.5>= 3.14.0, < 3.14.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify GitHub Enterprise Server versionAccess the GitHub Enterprise Server management console or use the administrative API to retrieve the installed version. On the management dashboard, navigate to the 'About' or 'Version' section to confirm the exact build number.Affected if The installed version falls into any of these ranges: < 3.11.6, >= 3.12.0 and < 3.12.10, >= 3.13.0 and < 3.13.5, or >= 3.14.0 and < 3.14.2
-
Determine if webhooks or message handling is enabledReview the GitHub Enterprise Server administrative settings to confirm whether incoming webhooks, outgoing webhooks, or message handling integrations are configured and active. Check under the repository or organization settings for webhook configurations.Affected if Webhooks or message handling features are enabled and the server version is within the affected ranges listed above
-
Review audit logs for suspicious identity property activityExamine the GitHub Enterprise Server audit log for entries containing unusual query selector patterns or identity property manipulations. Focus on entries related to message handling, webhooks, or API requests that may indicate DOM-based injection attempts.Affected if Audit logs show unexpected query selector activity or authentication token exfiltration attempts originating from user-controlled identity properties in message handling contexts
You are affected if GitHub Enterprise Server is running a version within the vulnerable ranges AND webhooks or message handling functionality is enabled, allowing user-supplied identity properties to reach the vulnerable code path.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped3.11.63.12.103.13.5
Upgrade GitHub Enterprise Server to version 3.11.16, 3.12.10, 3.13.5, 3.14.2, or 3.15.0 or later to patch this vulnerability.
GitHub Enterprise Server 3.15.0 (or 3.11.16/3.12.10/3.13.5/3.14.2 depending on your current branch)
- 1. Back up your current GitHub Enterprise Server data and configuration
- 2. Review the upgrade prerequisites for your current version in the GitHub Enterprise Server documentation
- 3. Download GitHub Enterprise Server 3.15.0 (or the appropriate fixed version for your branch: 3.11.16, 3.12.10, 3.13.5, or 3.14.2)
- 4. Perform the upgrade following the standard GitHub Enterprise Server upgrade procedure
- 5. Verify the upgrade was successful by checking the administrative dashboard
- 6. Confirm the installed version reflects the patched release
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Enterprise Server
Scoped from the published advisory
- Consultation4.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,152.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-10001 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-10001 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data