Loading vulnerability…
CVE-2019-1003001 is a sandbox bypass vulnerability in Jenkins Pipeline: Groovy Plugin 2.61 and earlier. The flaw affects Pipeline script handling in components including CpsFlowDefinition.java and CpsGroovyShellFactory.java, where unsafe Groovy AST transforming annotations can be processed during compilation of sandboxed Pipeline code. An attacker with Overall/Read permission can submit a crafted Pipeline script to an HTTP endpoint used for Pipeline validation or execution and bypass the intended Groovy sandbox restrictions. Successful exploitation can result in arbitrary code execution within the Jenkins controller JVM.
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 (1 hidden).
This repository contains a Metasploit module (jenkins_metaprogramming.rb) that exploits multiple vulnerabilities in Jenkins (CVE-2018-1000861, CVE-2019-1003000, CVE-2019-1003001, CVE-2019-1003002, CVE-2019-1003005, CVE-2019-1003029) to achieve unauthenticated remote code execution (RCE) by bypassing the Overall/Read ACL and leveraging Groovy metaprogramming. The exploit targets Jenkins version 2.137 and below, specifically when the Pipeline: Groovy Plugin 2.61 is installed. It provides two main attack vectors: (1) Unix In-Memory, which executes arbitrary shell commands in memory, and (2) Java Dropper, which delivers and executes a malicious JAR file via Groovy's @Grab annotation. The module is highly weaponized, allowing the attacker to select payloads (reverse shell, Meterpreter, etc.) and automatically handles the delivery and execution of the payload. The main endpoints targeted are Jenkins HTTP API routes related to user search and Groovy script compilation. The code is structured as a typical Metasploit module, with clear separation of check, exploit, and payload delivery logic.
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.
1 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.