Poll ScmApplication · Jenkins

CVE-2017-1000093

HIGH · 8.8 CVSS v3.0 Published 2017-10-05
Fix available
A fix is available. Upgrade to after 1.3.1 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Poll SCM Plugin for Jenkins did not enforce POST requests for its API endpoints, enabling Cross-Site Request Forgery (CSRF) attacks. Attackers could trigger polling of projects with known names by tricking authenticated users into visiting malicious pages, bypassing the plugin's permission system designed to control this functionality.

MitigationUpdate the Poll SCM Plugin to a version that requires POST requests for API calls. Additionally, ensure Jenkins' built-in CSRF protection is enabled.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Poll ScmApplication
Affected:<= 1.3.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Poll SCM Plugin is installed
    Log into Jenkins as an administrator, go to Manage Jenkins > Manage Plugins > Installed tab, and search for 'Poll SCM' in the list of installed plugins.
    Affected if The Poll SCM Plugin appears in the installed plugins list.
  2. Check installed Poll SCM Plugin version
    In the Installed plugins tab, locate the Poll SCM Plugin and note the version number displayed in the 'Version' column. Alternatively, run this Groovy script in Manage Jenkins > Script Console: Jenkins.instance.pluginManager.plugins.each { if (it.shortName == 'poll-scm') { println "Poll SCM Version: " + it.version } }
    Affected if The installed version is 1.3.1 or lower.
  3. Verify Jenkins CSRF protection is enabled
    Go to Manage Jenkins > Configure Global Security > CSRF Protection section. Confirm the 'Enable proxy compatibility' or default 'Prevent Cross Site Request Forgery exploits' checkbox is checked/enabled.
    Affected if CSRF protection is disabled or not configured.
  4. Identify jobs using Poll SCM triggers
    Run this Groovy script in Manage Jenkins > Script Console: Jenkins.instance.allItems.each { job -> if (job.hasProperty('pollSCM') || (job.triggers.values().any { it.class.name.contains('PollSCMTrigger') })) { println job.fullName } }
    Affected if Jobs exist that are configured with Poll SCM triggers.

You are affected if the Poll SCM Plugin version is 1.3.1 or lower, CSRF protection is disabled, and jobs using Poll SCM triggers exist in your Jenkins instance.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 1.3.1
Interim mitigation

Update the Poll SCM Plugin to a version that requires POST requests for API calls. Additionally, ensure Jenkins' built-in CSRF protection is enabled.

Fix this in Poll Scm Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-1000093 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-1000093 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data