dbcve.org
JenkinsApplication

CVE-2018-1000997

MEDIUM · 6.5 CVSS v3.0 Published 2019-01-23
Fix available
A fix is available. Upgrade to after 2.145 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
A path traversal vulnerability exists in the Stapler web framework used by Jenkins 2.145 and earlier, LTS 2.138.1 and earlier in core/src/main/java/org/kohsuke/stapler/Facet.java, groovy/src/main/java/org/kohsuke/stapler/jelly/groovy/GroovyFacet.java, jelly/src/main/java/org/kohsuke/stapler/jelly/JellyFacet.java, jruby/src/main/java/org/kohsuke/stapler/jelly/jruby/JRubyFacet.java, jsp/src/main/java/org/kohsuke/stapler/jsp/JSPFacet.java that allows attackers to render routable objects using any view in Jenkins, exposing internal information about those objects not intended to be viewed, such as their toString() representation.

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

A path traversal vulnerability in the Stapler web framework allows attackers to render routable Jenkins objects using arbitrary views, bypassing intended access controls and exposing internal object information (such as toString() representations) not meant for public viewing.

MitigationUpgrade Jenkins to version 2.146 or later (or LTS 2.138.2 or later) to patch the Stapler framework vulnerability.

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
JenkinsApplication
Affected:<= 2.138.1<= 2.145

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. Identify Jenkins version
    Navigate to Manage Jenkins > About Jenkins or access /api/json?tree=version endpoint. Alternatively, check the jenkins.war file version or systemd/service logs.
    Affected if The installed version is Jenkins <= 2.138.1 or Jenkins <= 2.145 (any version in the 2.x series up to those numbers)
  2. Confirm Stapler web framework is active
    Check if the Jenkins web interface is running and accessible. The Stapler framework handles URL routing in Jenkins. Verify by accessing the base Jenkins URL.
    Affected if Jenkins web interface is exposed and reachable (even on localhost)
  3. Check for anonymous or unauthenticated access
    Review security settings under Manage Jenkins > Configure Global Security. Verify whether anonymous users have any access permissions, or test accessing Jenkins URLs without credentials.
    Affected if Anonymous read access is enabled or the Jenkins UI is accessible without authentication
  4. Test for path traversal exposure
    Attempt to access known routable Jenkins objects via URL paths like /obj/{className} or /rss... or other non-standard paths. For example, try accessing internal object representations through the Stapler routing.
    Affected if The server returns internal object information (toString() representations) or unexpected view renders that should be restricted

If your Jenkins version is 2.138.1 or earlier, or 2.145 or earlier, AND the web interface is accessible, your environment may be vulnerable to this path traversal flaw in the Stapler framework.

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 2.145
Interim mitigation

Upgrade Jenkins to version 2.146 or later (or LTS 2.138.2 or later) to patch the Stapler framework vulnerability.

Fix this in Jenkins Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-1000997 — 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-2018-1000997 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