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.
References
Link | Resource |
---|---|
https://jenkins.io/security/advisory/2017-07-10/ | Vendor Advisory |
https://jenkins.io/security/advisory/2017-07-10/ | Vendor Advisory |
Configurations
History
21 Nov 2024, 03:04
Type | Values Removed | Values Added |
---|---|---|
References | () https://jenkins.io/security/advisory/2017-07-10/ - Vendor Advisory |
Information
Published : 2017-10-05 01:29
Updated : 2024-11-21 03:04
NVD link : CVE-2017-1000093
Mitre link : CVE-2017-1000093
CVE.ORG link : CVE-2017-1000093
JSON object : View
Products Affected
jenkins
- poll_scm
CWE
CWE-352
Cross-Site Request Forgery (CSRF)