dbcve.org
Configuration SlicingApplication · Jenkins

CVE-2021-21617

HIGH · 8.8 CVSS v3.1 Published 2021-02-24
Fix available
A fix is available. Upgrade to after 1.51 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
A cross-site request forgery (CSRF) vulnerability in Jenkins Configuration Slicing Plugin 1.51 and earlier allows attackers to apply different slice configurations.

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

A cross-site request forgery (CSRF) vulnerability in Jenkins Configuration Slicing Plugin versions 1.51 and earlier allows remote attackers to trick authenticated Jenkins users into unknowingly applying modified slice configurations via malicious requests.

MitigationUpgrade Jenkins Configuration Slicing Plugin to version 1.52 or later to remediate the CSRF vulnerability.

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
Configuration SlicingApplication
Affected:<= 1.51

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.1/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 Configuration Slicing Plugin is installed
    Navigate to Jenkins UI: Manage Jenkins > Manage Plugins > Installed tab, search for 'Configuration Slicing'. Alternatively, check if the plugin directory exists at $JENKINS_HOME/plugins/configuration-slicing/ or list installed plugins via CLI: jenkins-cli.jar or REST API at /pluginManager/api/json?tree=plugins[shortName,version]
    Affected if The plugin is not listed in installed plugins, indicating it is not present in the environment.
  2. Determine installed plugin version
    In Jenkins UI, click on the Configuration Slicing plugin entry in the Installed tab to view its version. Via CLI, inspect the plugin manifest: unzip -p $JENKINS_HOME/plugins/configuration-slicing/META-INF/MANIFEST.MF
    Affected if Version displayed is 1.51 or earlier, or the manifest shows a version <= 1.51.
  3. Confirm authenticated user access to slicing features
    Verify whether any Jenkins users or groups have permission to access Configuration Slicing features. Check under: Manage Jenkins > Configure Global Security > Authorization, or review job/configure permissions for users with Overall/Read and Job/Configure access. The vulnerability requires an authenticated user session.
    Affected if Any authenticated user (even limited) can access the Configuration Slicing functionality, enabling the CSRF attack vector.
  4. Check for slice configuration usage
    Look for the Configuration Slicing link in Jenkins sidebar: Click on 'Configuration Slicing' to see if any slice configurations exist. Navigate to the main Jenkins dashboard and check for 'Configuration Slicing' menu item.
    Affected if Slice configurations are actively defined or the plugin UI is accessible, meaning the vulnerable feature is enabled.

You are affected if the Configuration Slicing Plugin is installed with version 1.51 or earlier and users have authenticated access to the plugin's slicing features.

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.51
Interim mitigation

Upgrade Jenkins Configuration Slicing Plugin to version 1.52 or later to remediate the CSRF vulnerability.

Fix this in Configuration Slicing Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
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,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-21617 — 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-2021-21617 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