Vulnerability Description
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.
CVSS Score
HIGH
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Jenkins | Poll Scm | <= 1.3.1 |
Related Weaknesses (CWE)
References
- https://jenkins.io/security/advisory/2017-07-10/Vendor Advisory
- https://jenkins.io/security/advisory/2017-07-10/Vendor Advisory
FAQ
What is CVE-2017-1000093?
CVE-2017-1000093 is a vulnerability with a CVSS score of 8.8 (HIGH). 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 know...
How severe is CVE-2017-1000093?
CVE-2017-1000093 has been rated HIGH with a CVSS base score of 8.8/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2017-1000093?
Check the references section above for vendor advisories and patch information. Affected products include: Jenkins Poll Scm.