Threats / Jenkins / CVE-2015-5317
CVE-2015-5317
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-06-22
Jenkins User Interface (UI) vulnerability
Jenkins UI information disclosure vulnerability allows unauthorized users to view job and build names on Fingerprints pages, exposing sensitive project information.
Verdict
Today item — known-exploited.
An authenticated or unauthenticated attacker can enumerate restricted Jenkins jobs and builds through the Fingerprints feature, leading to information disclosure about project structure and activity.
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
4 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2023-05-12).
Probability (EPSS)
EPSS 0.22429 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Jenkins, Jenkins User Interface (UI). Confirm exact fixed builds in the vendor advisory.
Weakness (CWE)
Mapped to CWE-200 Information Exposure — weakness family: Authorization / access control.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I access the Jenkins Fingerprints pages to discover job and build names that should be restricted from my view.
Business
Confidential project names, build artifacts, and organizational structure become visible to unauthorized parties, compromising operational security.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I enumerate multiple restricted jobs and builds to map the CI/CD pipeline and identify high-value targets for further exploitation.
Business
Attackers gain reconnaissance data to plan targeted attacks against specific build systems or downstream deployment infrastructure.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05