← gociux.comall exploited CVEs

Exploited vulnerability · CISA KEV

Is CVE-2015-5317 exploited? Yes: in CISA KEV since 12 May 2023

Gociux · Jenkins User Interface (UI) · data: CISA KEV, CVE record, FIRST EPSS

Yes. CVE-2015-5317, Jenkins User Interface (UI) Information Disclosure Vulnerability, is being exploited in the wild. CISA added it to its Known Exploited Vulnerabilities catalog on 12 May 2023, 2725 days after it was published. It affects Jenkins User Interface (UI). If you run it, CISA's required action is: Apply updates per vendor instructions.

exploitedYesCISA KEV · 12 May 2023
ransomwareNot knownno confirmed use
EPSStop 5%very likely to be exploited
severity7.5CVSS 3.1 · high
US federal due2 Jun 2023BOD 22-01 deadline

What it is

Jenkins User Interface (UI) contains an information disclosure vulnerability that allows users to see the names of jobs and builds otherwise inaccessible to them on the "Fingerprints" pages.

VendorJenkins (6 exploited CVEs in KEV)
ProductJenkins User Interface (UI)
VulnerabilityJenkins User Interface (UI) Information Disclosure Vulnerability
WeaknessCWE-200
Published25 Nov 2015
Added to KEV12 May 2023
Reported by (CNA)redhat

What to do

  1. Check whether you run it. Look for Jenkins User Interface (UI) in your asset inventory, including appliances and cloud images. Stack check lists every exploited Jenkins CVE at once.
  2. Apply the fix. Apply updates per vendor instructions.
  3. If you can't patch today, take the affected service off the internet or restrict who can reach it, and check its logs for signs of compromise since 25 Nov 2015.
  4. Get told next time. Email alerts when CISA adds a CVE for Jenkins.

References

Questions

Is CVE-2015-5317 being exploited?

Yes. CISA added CVE-2015-5317 to the Known Exploited Vulnerabilities catalog on 12 May 2023, which means there is reliable evidence of exploitation in the wild.

Is CVE-2015-5317 used in ransomware attacks?

CISA does not list known ransomware use for it. That can change, and exploitation alone is reason to fix it first.

How do I fix CVE-2015-5317?

Apply updates per vendor instructions. Check Jenkins's advisory for the fixed versions, and if you can't patch quickly, restrict access to the affected Jenkins User Interface (UI) and watch it for signs of compromise.

Sources: CISA KEV (exploitation, ransomware use, required action, due date), the CVE record (publication date, CVSS, CNA), NVD and FIRST EPSS (live score). More: all KEV additions in May 2023 · Jenkins scorecard · act-now radar.

Running Jenkins in a regulated environment?

We check exposure across your estate, patch or mitigate with your team, and set up detection for what attackers do after exploiting it.

Get in touch →