A command injection vulnerability in the Management Console of GitHub Enterprise Server allowed an attacker with an editor role account to execute arbitrary commands, leading to privilege escalation. All versions prior to 3.11.3, 3.10.5, 3.9.8, and 3.8.13 are affected. The vulnerability was reported through the GitHub Bug Bounty program.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains two Python exploit scripts targeting critical vulnerabilities in GitHub Enterprise Server: CVE-2024-0200 and CVE-2024-0507. The structure is straightforward, with each exploit in its own file (CVE-2024-0200.py and CVE-2024-0507.py), a README.md with background and references, and an assets directory for images. CVE-2024-0200.py exploits an unsafe reflection vulnerability that allows an attacker with organization owner credentials to leak the ENTERPRISE_SESSION_SECRET and craft a malicious session cookie. This cookie, when sent to the server, triggers a Ruby Marshal deserialization vulnerability, resulting in remote code execution (RCE) as the server. The payload opens a reverse shell to an attacker-controlled IP and port. CVE-2024-0507.py exploits a command injection vulnerability in the management console's storage settings. By injecting a command into a POST parameter, the attacker can reset the root site admin password to a known value, effectively escalating privileges to site admin. The script automates login, CSRF token handling, payload delivery, and status checking. Both exploits require valid credentials and target network-accessible endpoints on the GitHub Enterprise Server web interface. The code is operational, automating the full exploitation process for each CVE. No fake or detection-only scripts are present.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.