JenkinsApplication
CVE-2015-5317
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 · uneditedThe Fingerprints pages in Jenkins before 1.638 and LTS before 1.625.2 might allow remote attackers to obtain sensitive job and build name information via a direct request.
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 confidenceAn information disclosure vulnerability in Jenkins' Fingerprints pages allows remote attackers to obtain sensitive job and build name information via direct requests. This affects Jenkins versions before 1.638 and LTS versions before 1.625.2. The vulnerability exposes internal build information that could aid further attacks.
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
<= 1.637<= 1.625.1
OpenshiftApplication
= 2.0<= 3.1CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Jenkins versionIn the Jenkins web UI, go to Manage Jenkins > About Jenkins. Alternatively, check the version displayed on the Jenkins login page.Affected if Version is 1.637 or earlier, or LTS version is 1.625.1 or earlier
-
Identify Red Hat OpenShift versionRun the command: openshift version, or check the installed package versionAffected if OpenShift version is 2.0 or 3.1 or earlier
-
Confirm Fingerprints functionality is in useNavigate to a build page and check if the Fingerprint icon/option is present, or check if any fingerprint records exist in the $JENKINS_HOME/fingerprints/ directoryAffected if Fingerprints feature is enabled and records exist
If the installed Jenkins version is 1.637 or earlier (or LTS 1.625.1 or earlier), or if OpenShift version is 2.0 to 3.1, and the Fingerprints feature is enabled, the environment is affected by this CVE.
Generated from the published advisory. Verify against your own configuration.
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.
dbcve · scopedUpgrade Jenkins to version 1.638 or later (or LTS 1.625.2 or later) to remediate this vulnerability.
Jenkins 1.638 (weekly) or Jenkins LTS 1.625.2 (LTS)
- 1. Back up your Jenkins configuration, jobs, and user data before upgrading
- 2. Identify whether you are running the weekly release or LTS (Long Term Support) release
- 3. If running weekly release, upgrade to Jenkins 1.638 or later
- 4. If running LTS release, upgrade to Jenkins LTS 1.625.2 or later
- 5. Restart the Jenkins service to apply the update
- 6. Verify the upgrade was successful by checking the Jenkins version at: /about/
- 7. Test that the fingerprint functionality works correctly and the information exposure is mitigated
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Jenkins
Exploited in the wild — priority engagement
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2015-5317 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2015-5317 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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