dbcve.org
JenkinsApplication

CVE-2018-1000410

HIGH · 7.8 CVSS v3.0 Published 2019-01-09
Fix available
A fix is available. Upgrade to after 2.145 or later.
See remediation →
80/100
Remediation priority · High
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
An information exposure vulnerability exists in Jenkins 2.145 and earlier, LTS 2.138.1 and earlier, and the Stapler framework used by these releases, in core/src/main/java/org/kohsuke/stapler/RequestImpl.java, core/src/main/java/hudson/model/Descriptor.java that allows attackers with Overall/Administer permission or access to the local file system to obtain credentials entered by users if the form submission could not be successfully processed.

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 credential information exposure vulnerability in Jenkins 2.145 and earlier (LTS 2.138.1 and earlier) and the Stapler framework allows attackers with Overall/Administer permission or local file system access to retrieve credentials that users entered if the form submission failed to process successfully. The vulnerability exists in RequestImpl.java and Descriptor.java where form data containing sensitive credentials is not properly cleared or protected upon submission failure.

MitigationUpgrade Jenkins to version 2.146 or LTS 2.138.2 or later. Until then, restrict Overall/Administer permissions strictly and limit file system access to trusted personnel only.

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:L/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 checks

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

  1. Identify Jenkins version
    Navigate to Manage Jenkins > About Jenkins or check the jenkins.war file version. Run: java -jar jenkins.war --version or check the bottom of the Jenkins dashboard.
    Affected if Version is 2.138.1 or earlier (LTS) or 2.145 or earlier (weekly)
  2. Confirm Stapler framework usage
    Jenkins uses the Stapler web framework by default. Check if the Stapler plugin is present or inspect HTTP responses for stapler-related headers.
    Affected if Stapler framework is enabled (default configuration)
  3. Verify credential storage
    Navigate to Manage Jenkins > Manage Credentials. Check if any credentials (passwords, API tokens, secrets, SSH keys) are stored in Jenkins.
    Affected if Credentials are stored in Jenkins credentials store
  4. Review Overall/Administer permissions
    Go to Manage Jenkins > Manage Users and check which users have Overall > Administer permission. Alternatively, inspect config.xml for users with permission element containing 'OverallAdminister'.
    Affected if More than one user or untrusted users have Overall/Administer permission
  5. Assess local file system access
    Check file system permissions on the Jenkins home directory (typically $JENKINS_HOME or /var/lib/jenkins). Determine if non-admin users can read configuration files.
    Affected if Non-admin users have read access to Jenkins configuration files

You are affected if running Jenkins version 2.138.1 or earlier (LTS) or 2.145 or earlier, and you have stored credentials in Jenkins with users possessing Overall/Administer permission or non-admin users having file system access to the Jenkins home directory.

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 LTS 2.138.2 or later. Until then, restrict Overall/Administer permissions strictly and limit file system access to trusted personnel only.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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