Loading vulnerability…
CVE-2019-1003030 is a sandbox bypass vulnerability in Jenkins Pipeline: Groovy Plugin affecting version 2.63 and earlier. The issue is associated with code in CpsGroovyShell.java and allows an attacker who can control Pipeline scripts to escape the intended Groovy sandbox restrictions and execute arbitrary code in the Jenkins controller JVM. Available information also characterizes the flaw as involving insecure deserialization. Successful exploitation breaks the trust boundary between sandboxed Pipeline execution and the Jenkins master process, enabling execution of attacker-controlled code with the privileges of the Jenkins service.
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.
2 valid exploits after Mallory filtered fakes, detection scripts, and README-only repos (1 hidden).
Repository contains a small standalone Python proof-of-concept exploit for a Jenkins 2.63 Script Security sandbox bypass. Structure is minimal: one code file (Poc.py) and one README. The Python script uses requests, urllib, and argparse to build and deliver a Groovy payload to Jenkins' SecureGroovyScript checkScript endpoint. The payload is a Groovy class whose constructor calls "<command>".execute(), enabling remote OS command execution on the Jenkins server. The script URL-encodes the entire Groovy source and sends it as the value parameter along with sandbox=true; it can also append a user-supplied Jenkins crumb parameter for CSRF-protected instances. It supports both GET and POST delivery, a single-command mode via -c, and an interactive shell-like loop when -c is omitted. The exploit first performs a GET to the base Jenkins URL to establish a session, then submits the malicious payload to the target path. Output handling is limited: the README and code both indicate command output is generally not returned, so operators are expected to verify execution through side effects or callbacks. The code appears duplicated in the latter half of Poc.py, likely accidental copy/paste rather than additional functionality. Overall, this is a real exploit PoC focused on web-based remote command execution against vulnerable Jenkins 2.63 instances, not a scanner or detection script.
This repository contains a single Python script, 'CVE-2019-1003030_Jenkins_RCE.py', which exploits CVE-2019-1003030 in Jenkins. The script automates the process of obtaining a Jenkins CSRF crumb, uploading a bash reverse shell script to a specified writeable folder on the Jenkins server, and then executing it via a crafted Groovy script payload. The exploit requires the attacker to provide the Jenkins URL, a writeable folder path on the target, and their own host and port for the reverse shell connection. The script interacts with the Jenkins REST API endpoints '/crumbIssuer/api/json' and '/securityRealm/user/admin/descriptorByName/org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SecureGroovyScript/checkScript'. The main capability is to achieve remote code execution and obtain a reverse shell on the Jenkins server. The repository is operational, providing a working exploit with a hardcoded reverse shell payload.
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.
4 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.