CSRF in Jenkins Poll Scm
CVE-2017-1000093
Poll SCM Plugin was not requiring requests to its API be sent via POST, thereby opening itself to Cross-Site Request Forgery attacks. This allowed attackers to initiate polling of projects with a known name. While Jenkins in general does not consider polling to be a protection-worthy action as it's similar to cache invalidation, the plugin specifically adds a permission to be able to use this functionality, and this issue undermines that permission.
Vulnerability class: CSRF (Cross-Site Request Forgery)
Published · last modified .
CVSS v3 metric
CVSS v3 base score 8.8 (High). Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H.
EPSS exploit prediction
EPSS: 0.007 (50.7th percentile), scored .
Very low probability of exploitation in the next 30 days; routine patching cadence is appropriate. 51st percentile — 50.7% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.
EPSS over last 30 days · oldest: 0.007 · newest: 0.007 · change: 0.000
Affected products
Weakness classification (CWE)
References
- jenkins.io/security/advisory/2017-07-10/ (Vendor Advisory)
Frequently asked questions
- What is CVE-2017-1000093?
- CVE-2017-1000093 is a high-severity vulnerability in Jenkins Poll Scm, classified under Cross-Site Request Forgery (CSRF). CVSS score: 8.8/10. Published 2017-10-05.
- How severe is CVE-2017-1000093?
- High severity. CVSS v3 base score is 8.8 out of 10.