dbcve.org
JenkinsApplication

CVE-2018-1000407

MEDIUM · 6.1 CVSS v3.0 Published 2019-01-09
Fix available
A fix is available. Upgrade to after 2.145 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 cross-site scripting vulnerability exists in Jenkins 2.145 and earlier, LTS 2.138.1 and earlier in core/src/main/java/hudson/model/Api.java that allows attackers to specify URLs to Jenkins that result in rendering arbitrary attacker-controlled HTML by Jenkins.

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

An XSS vulnerability in Jenkins core Api.java allows attackers to inject arbitrary HTML/JavaScript through specially crafted URLs. The vulnerability affects the URL rendering in the API, enabling stored XSS attacks against users who access attacker-controlled URLs.

MitigationUpgrade Jenkins to version 2.145+ or LTS 2.138.2+ to patch the vulnerable code in Api.java. If immediate upgrade is not feasible, implement URL parameter validation and deploy a WAF as a compensating control.

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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 installed Jenkins version
    Navigate to Manage Jenkins > About Jenkins or access /whoAmI/api/json endpoint. Alternatively, check the jenkins.war file metadata or the Jenkins startup logs.
    Affected if Version is 2.138.1 or lower, or 2.145 or lower (any version in the 2.x series at or below these thresholds)
  2. Identify if running LTS or weekly release
    Look at the version number format. LTS versions follow pattern like 2.x.x (e.g., 2.138.1). Weekly releases are milestone versions like 2.145.
    Affected if LTS releases at 2.138.1 or below, or weekly releases at 2.145 or below, are vulnerable
  3. Verify API endpoint is accessible
    Access the Jenkins API at /api/ on your Jenkins instance (e.g., http://yourjenkins/api/). The vulnerability exists in the URL rendering of this endpoint.
    Affected if The API endpoint is accessible to users (this is the default state for most Jenkins installations)

If your Jenkins version is 2.138.1 or lower (LTS) or 2.145 or lower (weekly), and the API is accessible, your environment is vulnerable to CVE-2018-1000407.

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.145+ or LTS 2.138.2+ to patch the vulnerable code in Api.java. If immediate upgrade is not feasible, implement URL parameter validation and deploy a WAF as a compensating control.

Fix this in Jenkins Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
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,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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