# CVE-2024-10001: Code Injection Vulnerability in GitHub Enterprise Server Allows Arbitrary Code Execution via Message Handling

> Attackers can execute arbitrary code and steal authentication tokens by exploiting a code injection flaw in GitHub Enterprise Server message handling.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:L/VA:N/SC:N/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 29 Jan 2025
- **Updated:** 12 Feb 2025
- **Also known as:** GHSA-998c-6m77-6859

## What is CVE-2024-10001?

CVE-2024-10001 is a high-severity code injection vulnerability in Github Enterprise Server, published on 29 Jan 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A 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.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2024-10001?

It affects 1 product.


Products: Github Enterprise Server.

## How do I fix CVE-2024-10001?

No fix has been published for CVE-2024-10001 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-10001 being exploited?

There is no known exploitation of CVE-2024-10001 in the wild and no public exploit code.

## Other vulnerabilities in Github Enterprise Server

- [CVE-2024-4985](https://insights.sbomify.com/CVE-2024-4985/): Auth bypass in Enterprise Server (critical 10.0)
- [CVE-2022-23739](https://insights.sbomify.com/CVE-2022-23739/): Missing authorization in GitHub Enterprise Server (critical 9.8)
- [CVE-2022-46255](https://insights.sbomify.com/CVE-2022-46255/): Improper Limitation of a Pathname to a Restricted Directory in GitHub Enterprise Server leading to RCE (critical 9.8)
- [CVE-2021-22869](https://insights.sbomify.com/CVE-2021-22869/): Improper access control in GitHub Enterprise Server allows self-hosted runners to execute outside their control group (critical 9.8)
- [CVE-2024-9487](https://insights.sbomify.com/CVE-2024-9487/): Auth bypass in Enterprise Server (critical 9.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-10001 and fix it if it is affected.

What it is: CVE-2024-10001 is a high-severity code injection vulnerability in Github Enterprise Server, published on 29 Jan 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-10001 in the wild and no public exploit code.

Affected product: Github Enterprise Server. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-10001/ (Markdown: https://insights.sbomify.com/CVE-2024-10001/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-10001
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-10001
- OSV: https://osv.dev/vulnerability/CVE-2024-10001

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-10001/
Summaries are generated and may contain mistakes; the official description above is the record.