Jenkins before versions 2.44 and 2.32.2 is vulnerable to an insufficient permission check. This allows users with permissions to create new items (e.g. jobs) to overwrite existing items they don't have access to (SECURITY-321).
CVE-2017-2599
MEDIUMNVD 5.45.4—Trending — 3 sources updated this week
EchelonGraph scoreMEDIUM confidence
This medium-severity CVE scores 5.4 under NVD CVSS v3. EPSS exploit probability: 1.1%, top 37% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
Triggered by: NVD CVSS baseline
Sources: epss, nvd
5.4
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 1%CVSS: 5.4Exploit: NoneExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.4
- EG Score
- 5.4(medium)
- EPSS
- 63.2%
- KEV
- Not listed
Published
April 11, 2018
Last Modified
November 21, 2024
References (8)
- secalert@redhathttp://www.securityfocus.com/bid/95949
- secalert@redhathttps://bugzilla.redhat.com/show_bug.cgi?id=CVE-2017-2599
- secalert@redhathttps://github.com/jenkinsci/jenkins/commit/4ed5c850b6855ab064a66d02fb338f366853ce89
- secalert@redhathttps://jenkins.io/security/advisory/2017-02-01/
- af854a3a-2127-422b-91ae-364da2661108http://www.securityfocus.com/bid/95949
- af854a3a-2127-422b-91ae-364da2661108https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2017-2599
- af854a3a-2127-422b-91ae-364da2661108https://github.com/jenkinsci/jenkins/commit/4ed5c850b6855ab064a66d02fb338f366853ce89
- af854a3a-2127-422b-91ae-364da2661108https://jenkins.io/security/advisory/2017-02-01/
Frequently asked(5)
What is CVE-2017-2599?
CVE-2017-2599 is a medium vulnerability published on April 11, 2018. Jenkins before versions 2.44 and 2.32.2 is vulnerable to an insufficient permission check. This allows users with permissions to create new items (e.g. jobs) to overwrite existing items they don't have access to (SECURITY-321).
When was CVE-2017-2599 disclosed?
CVE-2017-2599 was first published in the National Vulnerability Database on April 11, 2018, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2017-2599 actively exploited?
CVE-2017-2599 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 63.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2017-2599?
CVE-2017-2599 has a CVSS v3 base score of 5.4 (NVD).
How do I remediate CVE-2017-2599?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-2599, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2017-2599
Is Your Infrastructure Affected by CVE-2017-2599?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.