dbcve.org
ReleaseApplication · Jenkins

CVE-2018-1000013

HIGH · 8.8 CVSS v3.0 Published 2018-01-23
Fix available
A fix is available. Upgrade to after 2.9 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
Jenkins Release Plugin 2.9 and earlier did not require form submissions to be submitted via POST, resulting in a CSRF vulnerability allowing attackers to trigger release builds.

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 Jenkins Release Plugin versions 2.9 and earlier lack CSRF protection by not requiring form submissions to be submitted via POST. This allows attackers to craft malicious requests that trick authenticated Jenkins users into unknowingly triggering release builds without their consent.

MitigationUpgrade the Jenkins Release Plugin to version 2.10 or later, which implements POST requirement enforcement for form submissions to prevent CSRF attacks.

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
ReleaseApplication
Affected:<= 2.9

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 Jenkins Release Plugin is installed
    Navigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'Release' plugin, or check the plugins directory if you have CLI access
    Affected if The plugin appears in the installed plugins list
  2. Check the installed version of Release Plugin
    In the plugin manager, note the version number displayed next to the Release plugin; compare it against the affected range <= 2.9
    Affected if The installed version is 2.9 or earlier
  3. Identify if release jobs exist
    Review Jenkins jobs that use the Release plugin (jobs with release or deploy build steps configured); check job configuration pages for release-related build steps
    Affected if There are active jobs configured with release build steps that authenticated users can trigger
  4. Verify CSRF protection configuration
    Go to Manage Jenkins > Configure Global Security and check if CSRF protection is enabled (Default Crumb Issuer or similar)
    Affected if CSRF protection is disabled globally, though the plugin vulnerability exists regardless of this setting

You are affected if the Jenkins Release Plugin version is 2.9 or earlier and there are release jobs configured that authenticated users can access.

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 2.9
Interim mitigation

Upgrade the Jenkins Release Plugin to version 2.10 or later, which implements POST requirement enforcement for form submissions to prevent CSRF attacks.

Fix this in Release Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Get it on GitHub Scan in the browser

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-2018-1000013 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