Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2019-1003000: Groovy compile-time sandbox bypass in Jenkins Script Security Plugin

Published Jan 22, 2019 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS8.8High · v3.1
EPSS98.4%100th percentile
CISA KEVNoNot listed
In the wildReported7 exploitation records in Mallory
Vendors
Red HatJenkins
IdentifiersCVE-2019-1003000CWE-94

CVE-2019-1003000 is a sandbox bypass vulnerability in Jenkins Script Security Plugin 1.49 and earlier that allows attacker-supplied Groovy scripts to execute arbitrary code on the Jenkins controller JVM. Pipeline script validation invokes GroovyClassLoader.parseClass(), which can trigger compile-time metaprogramming outside Pipeline runtime sandbox controls. Using @GrabResolver and @Grab, an attacker can cause Jenkins to retrieve a malicious JAR whose Groovy Runner service definition triggers instantiation of an attacker-controlled class. Identified entry points include doCheckScriptCompile() and toJson().

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation executes arbitrary code on the Jenkins controller JVM outside the intended script sandbox. Exploitation has been associated with cryptocurrency-mining malware propagation, including Kerberods and Rocke campaigns. Chaining the vulnerability with an earlier Jenkins dynamic-routing ACL bypass can enable pre-authentication remote code execution.

Mitigation

If you can’t patch tonight, do this now.

Restrict Jenkins network access to trusted users and networks, enforce authentication and access controls, and limit who can submit sandboxed Groovy or Pipeline scripts. Filter unnecessary outbound access to untrusted dependency repositories and malware-hosting services. Access controls alone may be insufficient where the separate dynamic-routing ACL bypass remains unpatched.

Remediation

Patch, then assume compromise.

Apply vendor security updates to Jenkins Script Security Plugin and affected Jenkins components. The affected Script Security Plugin versions are 1.49 and earlier; an exact fixed version is not available in the supplied information. Ensure updates address all affected parser entry points, since another exploitable entry point was identified after the initial fix. Patch the separate dynamic-routing ACL bypass where applicable.

Public exploits

Exploits

3 exploits validated by Mallory's analysis. Hidden: 1 rejected by Mallory's analysis as not a working exploit; 2 not yet analyzed, such as Exploit-DB entries.

View more in app →
jenkins_metaprogramming.rbThis 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.Disclosed Jan 8, 2019 · Framework: metasploit · ruby · networkWeaponizedExploit-DevelopmentThis repository is a comprehensive collection of exploit and proof-of-concept (PoC) code targeting a variety of vulnerabilities across multiple platforms and products. The structure is organized into directories for HEVD (HackSysExtremeVulnerableDriver) kernel exploits (covering stack overflow, use-after-free, arbitrary write, type confusion, race condition, and stack overflow with GS), Metasploit modules (for erlang cookie RCE, pfSense graph injection, SyncBreeze buffer overflow), personal exploits (for DELL EMC OneFS, Nimsoft nimcontroller, SyncBreeze, Sysdig Monitor, VXSearch), and ported exploits (for Oracle 9i XDB, Allied Telesyn AT-TFTP, LabF nfsAxe, Jenkins, Allok AVI, MySQL UDF, and WebDAV). The main capabilities include local and remote privilege escalation, remote code execution, and information disclosure. The exploits use a variety of payloads, including custom shellcode, msfvenom-generated payloads, and ROP chains, and target both local and network attack vectors. Notable fingerprintable endpoints include device handles (e.g., \\.\HackSysExtremeVulnerableDriver), HTTP/FTP services, and specific file paths (e.g., .zshrc for persistence). The repository demonstrates advanced exploitation techniques and is suitable for research, education, and penetration testing purposes.wetw0rk · Disclosed Apr 26, 2017 · c · python · local · network · httpOperationalcve-2019-1003000-jenkins-rce-pocThis repository is a proof-of-concept (PoC) exploit for multiple Jenkins vulnerabilities (CVE-2019-1003000, CVE-2019-1003001, CVE-2019-1003002) that allow an attacker with Overall/Read and Job/Configure permissions to bypass the Groovy sandbox and execute arbitrary code on the Jenkins master or node. The main exploit is implemented in 'exploit.py', a Python script that connects to a target Jenkins instance using the 'python-jenkins' library, modifies a pipeline job to inject a malicious Groovy script, triggers a build, and retrieves the output of the executed system command from the job's console output. The payload leverages Groovy's AST transformation annotations (specifically '@Grab') to import the 'ProcBuilder' class from an external Maven repository, enabling execution of arbitrary shell commands. The repository also includes a sample vulnerable Jenkins environment under 'sample-vuln', which can be used for local testing. The exploit demonstrates full remote code execution (RCE) capabilities and can be used to run any system command, including spawning a reverse shell. The attack vector is network-based, targeting Jenkins HTTP endpoints. The repository is well-structured, with clear documentation and usage instructions in the README.adamyordan · Disclosed Feb 15, 2019 · python · groovy · networkPoC
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
JenkinsScript Securityapplication
Red HatOpenshift Container Platformapplication
FAQ

Frequently asked questions

Is CVE-2019-1003000 exploited in the wild?
Yes. As of Oct 16, 2026, Mallory has reports of exploitation in the wild.
Is there a public exploit for CVE-2019-1003000?
Yes. Mallory tracks 3 public exploits or proofs of concept for CVE-2019-1003000, the earliest disclosed Apr 26, 2017.
Is there a patch for CVE-2019-1003000?
Apply vendor security updates to Jenkins Script Security Plugin and affected Jenkins components. The affected Script Security Plugin versions are 1.49 and earlier; an exact fixed version is not available in the supplied information.
What products are affected by CVE-2019-1003000?
Jenkins Script Security and Red Hat Openshift Container Platform.
How severe is CVE-2019-1003000?
CVE-2019-1003000 has a CVSS v3.1 score of 8.8 (High) and an EPSS score of 98.4% (100th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

8 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+4 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidence2Every report linking this CVE to a named adversary.
Associated malware6Malware families linked to this CVE, with evidence and IOCs.
Detection signatures3YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.