dbcve.org
Script SecurityApplication · Jenkins

CVE-2017-1000095

MEDIUM · 6.5 CVSS v3.0 Published 2017-10-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
The default whitelist included the following unsafe entries: DefaultGroovyMethods.putAt(Object, String, Object); DefaultGroovyMethods.getAt(Object, String). These allowed circumventing many of the access restrictions implemented in the script sandbox by using e.g. currentBuild['rawBuild'] rather than currentBuild.rawBuild. Additionally, the following entries allowed accessing private data that would not be accessible otherwise due to script security: groovy.json.JsonOutput.toJson(Closure); groovy.json.JsonOutput.toJson(Object).

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 confidence

Jenkins script security sandbox whitelist contained unsafe methods (getAt/putAt) that allowed bypassing access restrictions via bracket notation (currentBuild['rawBuild'] instead of currentBuild.rawBuild), and JsonOutput methods that exposed private data. This enabled malicious scripts to access protected objects and circumvent sandboxed security.

MitigationUpdate Jenkins and the Script Security Plugin to versions that remove these methods from the default whitelist, then review existing scripts for usage of these bypass techniques.

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
Affected:= 1.34

CVSS 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
None
Availability
None

CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Check Script Security plugin version
    Navigate to Jenkins Manage Plugins > Installed tab and locate the Script Security plugin, or check the plugin's manifest file (_MANIFEST.MF) in the plugin directory
    Affected if The installed version is 1.34, as this specific version contains the unsafe whitelist entries
  2. Confirm script security sandbox is enabled
    Look for pipelines or scripts that use the 'script' directive with sandbox mode enabled, typically indicated by '@Library(...) _' imports or 'pipeline { agent any; stages { stage('Build') { steps { script { ... } } } } }' syntax in Jenkinsfiles
    Affected if Sandbox mode is enabled, as the vulnerability only allows bypassing sandbox restrictions; non-sandboxed scripts are not affected by this whitelist bypass
  3. Inspect scripts for bracket notation bypass
    Search Groovy scripts, Jenkinsfiles, and saved scripts for patterns like currentBuild['rawBuild'], currentBuild['rawBuild'].getExternal(), or any object['property'] access where the object is a protected Jenkins internal (currentBuild, build, manager, etc.)
    Affected if Scripts contain bracket notation access to protected Jenkins objects (currentBuild, this, etc.) that would normally be restricted by the sandbox
  4. Check for JsonOutput usage in sandboxed contexts
    Search for 'JsonOutput.toJson' or 'JsonOutput.prettyPrint' calls within sandboxed script blocks or Jenkinsfile scripts
    Affected if Sandbox-enabled scripts use JsonOutput methods to serialize objects that may contain private Jenkins internal data

User is affected if running Script Security plugin version 1.34 with sandbox-enabled scripts that contain bracket notation on protected objects or use JsonOutput methods

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Jenkins and the Script Security Plugin to versions that remove these methods from the default whitelist, then review existing scripts for usage of these bypass techniques.

Fix this in Script Security Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA3.0 h
10.0 hours of engineering $1,720
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-1000095 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-1000095 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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