{"id":"CVE-2017-1000093","published":"2017-10-04T01:00:00Z","modified":"2024-08-05T21:53:06Z","title":"Poll SCM Plugin was not requiring requests to its API be sent via POST, thereby opening itself to Cross-Site Request…","vendor":null,"product":null,"tier":"tail","description":{"text":"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.","provenance":"source","from":"CVE.org"},"cvss":null,"epss":{"score":0.00678,"percentile":0.53264,"provenance":"source"},"cwes":[],"references":[{"url":"https://jenkins.io/security/advisory/2017-07-10/","tags":["x_refsource_CONFIRM"]}],"priority":{"score":10.7,"factors":[{"name":"EPSS percentile","points":10.65}]},"affected":[{"ecosystem":"Maven","package":"org.jenkins-ci.plugins:pollscm","vulnerableRanges":["<1.3.1"],"patched":["1.3.1"],"from":["GHSA-fv3c-6cw7-2qcq"],"provenance":"source"}],"summary":{"text":"The Poll SCM plugin for Jenkins does not require its API requests to be sent via POST, which leaves it open to Cross-Site Request Forgery. An attacker can exploit this to trigger polling of projects whose names they know, bypassing the permission the plugin is meant to enforce for that action.","provenance":"ai","model":"claude-haiku-5-5","generatedAt":"2026-11-20T22:09:51Z"},"euvd":{"id":"EUVD-2022-3831","exploited":false,"provenance":"source"}}