Auth bypass in Jenkins
CVE-2017-2599
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).
Vulnerability class: Broken Access Control
EPSS: 0.011 (63.3th percentile) — read the EPSS interpretation.
CVSS v3 metric
CVSS v3 base score 5.4 (Medium). Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N.
Affected products
- Jenkins
- [Unknown] Jenkins — versions jenkins 2.32.2, jenkins 2.44
Weakness classification (CWE)
Public proof-of-concept exploits
References
- secalert@redhat.com (VDB Entry, Third Party Advisory, vdb-entry, x_refsource_BID)
- secalert@redhat.com (x_refsource_CONFIRM, Vendor Advisory)
- secalert@redhat.com (x_refsource_CONFIRM, Third Party Advisory, Issue Tracking)
- secalert@redhat.com (x_refsource_CONFIRM, Patch, Third Party Advisory)
Frequently asked questions
- What is CVE-2017-2599?
- CVE-2017-2599 is a medium-severity vulnerability in Jenkins, classified under Incorrect Authorization. CVSS score: 5.4/10. Published 2018-04-11.
- How severe is CVE-2017-2599?
- Medium severity. CVSS v3 base score is 5.4 out of 10.
- Is CVE-2017-2599 known to be exploited?
- 1 public proof-of-concept repositories are indexed. Not currently listed in the CISA KEV catalog.