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.
Published: 2017-10-04
Score: 8.8 High
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Analysis and contextual insights are available on OpenCVE Cloud.

Remediation

No vendor fix or workaround currently provided.

Additional remediation guidance may be available on OpenCVE Cloud.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
EUVD EUVD 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.
Github GHSA Github GHSA GHSA-fv3c-6cw7-2qcq Jenkins Poll SCM Plugin vulnerable to Cross-Site Request Forgery
History

No history.

Subscriptions

Jenkins Poll Scm
cve-icon MITRE

Status: PUBLISHED

Assigner: mitre

Published:

Updated: 2024-08-05T21:53:06.517Z

Reserved: 2017-07-13T00:00:00.000Z

Link: CVE-2017-1000093

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Modified

Published: 2017-10-05T01:29:03.807

Modified: 2026-05-13T00:24:29.033

Link: CVE-2017-1000093

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

No data.

Weaknesses