Config File ProviderApplication · Jenkins
CVE-2021-21644
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 · uneditedA cross-site request forgery (CSRF) vulnerability in Jenkins Config File Provider Plugin 3.7.0 and earlier allows attackers to delete configuration files corresponding to an attacker-specified ID.
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 confidenceJenkins Config File Provider Plugin 3.7.0 and earlier lacks CSRF protection on a form action that deletes configuration files. Attackers can trick authenticated Jenkins users into unknowingly sending requests that delete attacker-specified configuration files by exploiting the missing token validation on the delete operation.
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
Config File ProviderApplication
<= 3.7.0CVSS 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
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L
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 checksWork through these to decide whether this CVE applies to you.
-
Verify Config File Provider plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'Config File Provider', or use the Jenkins CLI: java -jar jenkins-cli.jar list-plugins | grep -i 'config file provider'Affected if The plugin is not installed - not affected. If installed, continue to version check.
-
Identify the installed version of Config File ProviderIn the Manage Plugins > Installed page, locate Config File Provider and note the Version column. Alternatively, check the plugin's manifest file at $JENKINS_HOME/plugins/config-file-provider/META-INF/MANIFEST.MFAffected if Version cannot be determined - manual verification required. If version is readable, proceed to compare against affected range.
-
Compare installed version against affected rangeCheck if the installed version is 3.7.0 or earlier. The affected range is any version <= 3.7.0Affected if Installed version is 3.7.0 or earlier - affected by this CVE. Installed version is 3.7.1 or later - not affected by this specific vulnerability.
-
Verify CSRF protection configurationNavigate to Manage Jenkins > Configure Global Security. Under CSRF Protection, verify if CrumbIssuer is enabled. While this is a mitigation, its absence from the default configuration contributed to the severity of this issue.Affected if This check helps confirm exposure level but does not change whether the vulnerable plugin version is present.
A user is affected if Jenkins Config File Provider Plugin version 3.7.0 or earlier is installed and the plugin is in use, regardless of CSRF configuration, as the plugin itself lacks the protection.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade Jenkins Config File Provider Plugin to version 3.7.1 or later to receive the CSRF protection fix. Additionally, enable Jenkins' built-in CrumbIssuer for comprehensive CSRF defense across the instance.
Fix this in Config File Provider
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-21644 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-21644 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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