GroovyApplication · Jenkins
CVE-2019-1003006
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA sandbox bypass vulnerability exists in Jenkins Groovy Plugin 2.0 and earlier in src/main/java/hudson/plugins/groovy/StringScriptSource.java that allows attackers with Overall/Read permission to provide a Groovy script to an HTTP endpoint that can result in arbitrary code execution on the Jenkins master JVM.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Jenkins Groovy Plugin 2.0 and earlier contains a sandbox bypass vulnerability in StringScriptSource.java that allows attackers with Overall/Read permission to submit arbitrary Groovy scripts via HTTP endpoint, resulting in code execution on the Jenkins master JVM.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
GroovyApplication
<= 2.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check if Jenkins Groovy Plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab, or use the Jenkins CLI: java -jar jenkins-cli.jar list-plugins GroovyAffected if The Groovy plugin is not listed in installed plugins
-
Determine the installed Groovy Plugin versionIn the Jenkins UI, go to Manage Jenkins > Manage Plugins > Installed tab and find the Groovy plugin version in the list. Or check the plugin manifest file: $JENKINS_HOME/plugins/groovy/META-INF/MANIFEST.MFAffected if The installed version is 2.0 or earlier
-
Verify Overall/Read permission is granted to usersGo to Manage Jenkins > Manage Users, and then check authorization settings at Manage Jenkins > Configure Global Security. Look for users or groups granted Overall/Read permission.Affected if Any user or group has Overall/Read permission enabled (this permission is required for the exploit to work)
-
Check if Groovy script HTTP endpoint is accessibleAttempt to access the endpoint: http://JENKINS_URL/scriptText/ or verify the StrutsScriptSource API endpoint exists by checking available URLs under the Jenkins core. This is typically exposed at /script/ or /scriptText/Affected if The Groovy script endpoint is reachable without additional authentication beyond Overall/Read
You are affected if the Groovy Plugin version is 2.0 or earlier AND users with Overall/Read permission exist in your Jenkins instance.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade Jenkins Groovy Plugin to version 2.1 or later which contains the security fix, and restrict Overall/Read permissions to only necessary users.
Fix this in Groovy
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-1003006 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-1003006 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data