CVE-2017-1000093

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.

Category

8.8
CVSS
Severity: High
CVSS 3.0 •
CVSS 2.0 •
EPSS 0.06%
Vendor Advisory jenkins.io
Affected: n/a n/a
Published at:
Updated at:

References

Link Tags
https://jenkins.io/security/advisory/2017-07-10/ vendor advisory

Frequently Asked Questions

What is the severity of CVE-2017-1000093?
CVE-2017-1000093 has been scored as a high severity vulnerability.
How to fix CVE-2017-1000093?
To fix CVE-2017-1000093, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2017-1000093 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2017-1000093 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.