dbcve.org
Script SecurityApplication · Jenkins

CVE-2017-1000505

MEDIUM · 6.5 CVSS v3.0 Published 2018-01-25
Fix available
A fix is available. Upgrade to after 1.36 or later.
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
In Jenkins Script Security Plugin version 1.36 and earlier, users with the ability to configure sandboxed Groovy scripts are able to use a type coercion feature in Groovy to create new `File` objects from strings. This allowed reading arbitrary files on the Jenkins master file system. Such a type coercion is now subject to sandbox protection and considered to be a call to the `new File(String)` constructor for the purpose of in-process script approval.

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 Plugin versions 1.36 and earlier allowed sandboxed Groovy script users to exploit Groovy's type coercion feature to create File objects from strings, bypassing sandbox protections. This enabled arbitrary file read access on the Jenkins master file system. The vulnerability is now mitigated by treating such type coercion as a constructor call requiring sandbox approval.

MitigationUpgrade Jenkins Script Security Plugin to version 1.37 or later. Review and re-approve any existing sandboxed Groovy scripts that may have been using File object creation via type coercion.

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.36

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. Locate the Script Security Plugin version
    Navigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab and find 'Script Security Plugin' in the list. Note the version number displayed in the Version column.
    Affected if The installed version is 1.36 or earlier (e.g., 1.36, 1.35, 1.34, etc.)
  2. Verify plugin version via CLI
    Run the Jenkins CLI command: java -jar jenkins-cli.jar -s http://[jenkins-url] list-plugins | grep 'script-security' or access the plugin directory and read the manifest if CLI access is unavailable.
    Affected if The returned version is 1.36 or lower.
  3. Confirm Groovy sandbox execution is in use
    Review any configured jobs or pipelines that use the Groovy sandbox feature. Check job configurations for 'Use Groovy Sandbox' checkbox enabled in the 'Process Groovy Script' or 'Groovy' build steps.
    Affected if Sandboxed Groovy script execution is enabled and actively used in any job or pipeline configuration.
  4. Audit existing approved scripts
    Navigate to Manage Jenkins > In-process Script Approval (if available) and review any approved scripts. Look for scripts that may create File objects from string literals via type coercion.
    Affected if Approved scripts exist that perform File operations or could utilize the type coercion to bypass sandbox protections.

A user is affected if the Script Security Plugin version is 1.36 or earlier AND sandboxed Groovy script execution is enabled in their Jenkins environment.

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
Upgrade available Upgrade to a release after 1.36
Interim mitigation

Upgrade Jenkins Script Security Plugin to version 1.37 or later. Review and re-approve any existing sandboxed Groovy scripts that may have been using File object creation via type coercion.

Fix this in Script Security Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

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-1000505 — 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-1000505 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