Script SecurityApplication · Jenkins
CVE-2018-1000865
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 Script Security Plugin 1.47 and earlier in groovy-sandbox/src/main/java/org/kohsuke/groovy/sandbox/SandboxTransformer.java that allows attackers with Job/Configure permission to execute arbitrary code on the Jenkins master JVM, if plugins using the Groovy sandbox are installed.
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 confidenceA sandbox bypass vulnerability in Jenkins Script Security Plugin 1.47 and earlier in the SandboxTransformer.java allows attackers with Job/Configure permission to execute arbitrary code on the Jenkins master JVM by circumventing Groovy sandbox restrictions when plugins using the Groovy sandbox are installed.
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
Script SecurityApplication
<= 1.47
Openshift Container PlatformApplication
= 3.11CVSS 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.0/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.
-
Identify Script Security Plugin versionLocate the Jenkins Script Security plugin installation directory (typically $JENKINS_HOME/plugins/script-security/) and check the plugin's manifest file (META-INF/MANIFEST.MF) or the plugin's .hpi file for the version attributeAffected if The reported version is 1.47 or earlier
-
Check Jenkins versionAccess Jenkins management console or check $JENKINS_HOME/war/META-INF/MANIFEST.MF for the Jenkins versionAffected if Jenkins is running and the Script Security Plugin version cannot be separately determined (for OpenShift Container Platform 3.11 environments)
-
Verify Groovy sandbox is enabledReview job configurations that use Groovy scripts (look for 'Use Groovy Sandbox' checkbox in job configuration under 'Build Steps' or 'Pipeline' sections)Affected if Groovy sandbox protection is enabled for any job configuration, as the bypass specifically circumvents this protection
-
Review Job/Configure permission assignmentsCheck Jenkins authorization matrix or role-based access control (RBAC) settings to identify which users or groups possess Job/Configure or Item/Configure permissionsAffected if Any user or service account other than administrators has Job/Configure permission, as this is the privilege level required to exploit the sandbox bypass
You are affected if the Script Security Plugin version is 1.47 or earlier (or if you are on OpenShift Container Platform 3.11) AND users with Job/Configure permission exist AND Groovy sandbox is in use.
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 Script Security Plugin to version 1.48 or later to patch the sandbox bypass vulnerability.
Fix this in Script Security
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing3.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,936.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-1000865 — 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-2018-1000865 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