Loading vulnerability…
Jenkins Pipeline: Groovy Plugin 3990.vd281dd77a_388 and earlier, except 3975.3977.v478dd9e956c3, fails to verify whether the main Pipeline script (Jenkinsfile) associated with a rebuilt build is currently approved. As a result, when a user rebuilds a previous build, the plugin may execute a Jenkinsfile that has since become unapproved without re-checking script approval status. This creates an authorization/approval bypass in the rebuild path for Pipeline jobs.
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 provides a proof-of-concept (PoC) exploit for CVE-2024-52550, a directory traversal vulnerability affecting Jenkins or similar web applications exposing a '/static/' endpoint. The main file, 'exploit.py', allows the user to either start a local vulnerable server for testing or to test a remote target for the vulnerability. The exploit works by sending a GET request to the target's '/static/../../../../etc/passwd' path, attempting to read the sensitive /etc/passwd file. If the response contains 'root:x', the script reports the target as potentially vulnerable. The repository consists of a README and a single Python exploit script, with the latter containing both the exploit logic and a minimal vulnerable server for demonstration purposes. No hardcoded IPs or domains are present; the user supplies the target URL interactively.
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.
3 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.