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.
Metrics
Affected Vendors & Products
Advisories
Source | ID | Title |
---|---|---|
![]() |
EUVD-2022-3831 | 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. |
![]() |
GHSA-fv3c-6cw7-2qcq | Jenkins Poll SCM Plugin vulnerable to Cross-Site Request Forgery |
Fixes
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
Link | Providers |
---|---|
https://jenkins.io/security/advisory/2017-07-10/ |
![]() ![]() |
History
No history.

Status: PUBLISHED
Assigner: mitre
Published:
Updated: 2024-08-05T21:53:06.517Z
Reserved: 2017-07-13T00:00:00
Link: CVE-2017-1000093

No data.

Status : Deferred
Published: 2017-10-05T01:29:03.807
Modified: 2025-04-20T01:37:25.860
Link: CVE-2017-1000093

No data.

No data.