Approved changes feed: RSS · Atom
cpe:2.3:a:jenkins:poll_scm:*:*:*:*:*:jenkins:*:*
part: a version: * update: *
| Vendor | Jenkins (d708d718-2e77-5ca3-ae9c-38ee4d256744) |
|---|---|
| Product | Poll Scm (0aae6cf1-7adf-5357-a871-5a6bf8f0adb4) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | jenkins |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2017-1000093 |
vulnerable | 2026-06-08 05:08:33.923796 |
Details available
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-04T01:00:00.000Z
Updated: 2024-08-05T21:53:06.517Z Reference links |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.