# CVE-2015-5317: Jenkins discloses project names via fingerprints

Source: https://junglewise.ai/threats/cve-2015-5317-jenkins-user-interface-ui-information-disclosure-vulnerability  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2022-05-13. Updated: 2026-05-10  
License: CC BY 4.0 with a link back

CVE-2015-5317 · Severity: critical · CVSS 3.1 · Exploited in the wild · Published 2022-05-13

The Fingerprints pages in Jenkins allow remote attackers to obtain sensitive job and build name information via direct requests. This information disclosure occurs because the UI fails to properly restrict access to metadata for jobs and builds that should otherwise be inaccessible to the user.

Technologies: [org.jenkins-ci.main:jenkins-core (Maven)](https://junglewise.ai/threats/technologies/org-jenkins-ci-main-jenkins-core). Vendors: [Jenkins](https://junglewise.ai/threats/vendors/jenkins), [Maven](https://junglewise.ai/threats/vendors/maven).

## Quick answers

**Is CVE-2015-5317 exploited in the wild?** Yes. CVE-2015-5317 is known to be exploited in the wild, first recorded on 12 May 2023. Treat it as urgent.

**How severe is CVE-2015-5317?** Critical severity, with a CVSS score of 3.1, published 13 May 2022.

**Which products and versions are affected?** org.jenkins-ci.main:jenkins-core (Maven) ECOSYSTEM:introduced=0,fixed=1.625.2.

**Is there a fix for CVE-2015-5317?** Yes. org.jenkins-ci.main:jenkins-core (Maven): upgrade to 1.625.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2015-5317 attacked?** It is attacked over the network, in a network appliance.

**Am I affected by CVE-2015-5317?** Check whether you run Jenkins User Interface (UI) or org.jenkins-ci.main:jenkins-core (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- org.jenkins-ci.main:jenkins-core (Maven): upgrade to 1.625.2 or later

  ```sh
  # set org.jenkins-ci.main:jenkins-core to 1.625.2 in your pom.xml or build.gradle
  ```


## Affected products

- Jenkins Jenkins before 1.638
- Jenkins Jenkins LTS before 1.625.2
- Red Hat OpenShift Enterprise 2.0, 3.1

## Identifiers

- CVE-2015-5317
- GHSA-8pqx-3rxx-f5pm

## Timeline

- 2015-11-11: advisory: Jenkins Security Advisory 2015-11-11 published
- 2023-05-12: kev added: Added to CISA Known Exploited Vulnerabilities Catalog
- 2023-05-12: disclosed

## Related threats

- [Jenkins plaintext secret storage in job config.xml submissions](https://junglewise.ai/threats/cve-2026-53442-jenkins-plaintext-secret-storage-in-job-config-xml-submissions)
- [Jenkins stored XSS in node offline cause description](https://junglewise.ai/threats/cve-2026-53441-jenkins-stored-xss-in-node-offline-cause-description)
- [Jenkins open redirect in Delegate to servlet container security realm](https://junglewise.ai/threats/cve-2026-53440-jenkins-open-redirect-in-delegate-to-servlet-container-security)
- [Jenkins missing permission checks in user profile endpoints](https://junglewise.ai/threats/cve-2026-53439-jenkins-missing-permission-checks-in-user-profile-endpoints)
- [Jenkins missing permission check in queue item cancellation](https://junglewise.ai/threats/cve-2026-53438-jenkins-missing-permission-check-in-queue-item-cancellation)