Loading vulnerability…
CVE-2024-0200 is an unsafe reflection vulnerability in GitHub Enterprise Server and GitHub.com arising from use of a user-controlled identifier in a Ruby reflection call on a Repository object within the organizations actions settings flow. In the vulnerable path, the repository identifier key is derived from the rid_key request parameter and passed to a method that invokes repository.send without sufficient validation, enabling arbitrary invocation of accessible zero-argument methods, including methods with default arguments. The vulnerable rendering path returns the invoked method result in the repository items response. Researchers demonstrated impact by invoking a Repository method that traverses the Git RPC backend and returns process metadata containing the environment supplied to a spawned git process, thereby disclosing the Rails process environment. On GitHub Enterprise Server, the disclosed environment can include sensitive application secrets that enable further escalation to remote code execution. GitHub stated the issue affects GitHub Enterprise Server instances with GitHub Actions enabled and fixed it in 3.8.13, 3.9.8, 3.10.5, and 3.11.3; all versions prior to 3.12 were affected.
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.
6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A vulnerability identifier mentioned only in passing without any substantive context in this reference.
A CVE mentioned only in the title of another pull request; no vulnerability details are provided in this content.
A vulnerability detection template issue centered on CVE-2024-0200 where setup-stage matchers in a Nuclei exploit flow caused false positive critical findings against GitHub Enterprise hosts unless the final exploit evidence was present. The exploit stage requires HTTP 500 and an interactsh DNS callback as evidence of the reflection injection.
An arbitrary file write vulnerability in ThinkPHP 6 referenced through a Nuclei detection template named thinkphp6-arbitrary-write; the content discusses a bug in the detection template rather than new exploitation details about the vulnerability itself.
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.