dbcve.org
JenkinsApplication

CVE-2015-7539

HIGH · 7.5 CVSS v3.0 Published 2016-02-03
Fix available
A fix is available. Upgrade to after 1.639 or later.
See remediation →
82/100
Remediation priority · High
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
The Plugins Manager in Jenkins before 1.640 and LTS before 1.625.2 does not verify checksums for plugin files referenced in update site data, which makes it easier for man-in-the-middle attackers to execute arbitrary code via a crafted plugin.

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

The Jenkins Plugins Manager before version 1.640 (or LTS 1.625.2) fails to verify checksums for plugin files retrieved from update sites. This allows man-in-the-middle attackers to substitute malicious plugin files during transit, enabling arbitrary code execution on the Jenkins server.

MitigationUpgrade Jenkins to version 1.640 or later (LTS 1.625.2 or later) to enable plugin checksum verification.

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:<= 1.639<= 1.625.1
OpenshiftApplication
Affected:= 2.0= 3.1

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

CVSS:3.0/AV:N/AC:H/PR:N/UI:R/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. Check installed Jenkins version
    Run 'java -jar jenkins.war --version' or check the Jenkins UI at /about/ to find the exact version number
    Affected if version is 1.639 or lower, or LTS version is 1.625.1 or lower
  2. Identify configured update centers
    Navigate to Manage Jenkins > Manage Plugins > Advanced tab and review the 'Update Site' URL settings
    Affected if any update site URL is configured pointing to default Jenkins update center or custom update sites
  3. Check for installed plugins from update sites
    Navigate to Manage Jenkins > Manage Plugins > Installed tab to list plugins installed from update centers
    Affected if any plugins are installed that were downloaded from update sites rather than bundled or manually uploaded

User is affected if running Jenkins version 1.639 or earlier (or LTS 1.625.1 or earlier) AND has plugins installed from configured update centers, as the MITM vulnerability allows substitution of plugin files during download.

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.639
Interim mitigation

Upgrade Jenkins to version 1.640 or later (LTS 1.625.2 or later) to enable plugin checksum verification.

Fix this in Jenkins Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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