How severe is CVE-2015-5317?

CVE-2015-5317 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2015-5317?

Affected package information for CVE-2015-5317 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2015-5317?

No fixed version has been published for CVE-2015-5317 yet. Monitor the advisory for updates, apply mitigations recommended by the vendor, and use O3 Security to track when a fix becomes available in your stack.

Is CVE-2015-5317 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2015-5317, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2015-5317?

CVE-2015-5317 has an EPSS (Exploit Prediction Scoring System) score of 39.7%, placing it in the 97th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score warrants monitoring and prompt remediation.

Is CVE-2015-5317 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2015-5317 (Jenkins User Interface (UI) Information Disclosure Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2023-05-12. CISA required all US federal civilian agencies to remediate this vulnerability by 2023-06-02. The required action was: Apply updates per vendor instructions. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2015-5317?

CVE-2015-5317 is classified as Information Exposure (CWE-200). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Which products and versions are affected by CVE-2015-5317?

CVE-2015-5317 affects jenkins jenkins; redhat openshift (1 version, e.g. 2.0). Check the affected-products list on this page against your deployed version to confirm exposure.

When was CVE-2015-5317 published, and has it been updated?

CVE-2015-5317 was published on November 25, 2015 and was last updated on April 22, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CISA KEV·Added 2023-05-12 — agencies required to remediate by 2023-06-02

CVE-2015-5317

HIGH

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.

Published

Nov 25, 2015

Updated

Apr 22, 2026

Affected

0 pkgs

Patched

None yet

Exploits

1 known

EPSS Exploitation Probability

via FIRST.org ↗

39.7%probability of exploitation in next 30 days

Moderate Risk97th percentile0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

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.

Affected Products

2 products · 4 configurations

Application

jenkinsjenkins

≤ 1.625.1

range

Application

openshiftredhat

≤ 3.1

1 version

2.0

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

The Fingerprints pages in Jenkins before 1.638 and LTS before 1.625.2 mi…

cisa.govCISAMay 2023

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is CVE-2015-5317 in your stack?

O3 detects CVE-2015-5317 across dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my stack How O3 SCA works