Config File ProviderApplication · Jenkins
CVE-2021-21643
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 · uneditedJenkins Config File Provider Plugin 3.7.0 and earlier does not correctly perform permission checks in several HTTP endpoints, allowing attackers with global Job/Configure permission to enumerate system-scoped credentials IDs of credentials stored in Jenkins.
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 · moderate confidenceJenkins Config File Provider Plugin versions 3.7.0 and earlier contains improper permission checks in multiple HTTP endpoints. Attackers with global Job/Configure permission can enumerate system-scoped credentials IDs stored in Jenkins, leading to information disclosure of credential identifiers.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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 Jenkins > Manage Jenkins > Manage Plugins > Installed tab, or use the Jenkins CLI: java -jar jenkins-cli.jar list-plugins | grep -i 'config-file-provider'Affected if The plugin is not listed or shows as not installed, then the vulnerability does not apply
-
Check installed plugin versionIn Manage Plugins > Installed, find Config File Provider and read the Version column. Alternatively, check the plugin's WEB-INF/plugins/config-file-provider.jpi or .hpi file for the version manifestAffected if Version is 3.7.0 or earlier (any version <= 3.7.0 is affected)
-
Identify users with global Job/Configure permissionNavigate to Jenkins > Manage Jenkins > Manage Users, then go to Manage Jenkins > Configure Global Security > Authorization section. Review which users or groups have the Overall > Administer or Job > Configure permission at the global levelAffected if Untrusted or unauthorized users have global Job/Configure permission, enabling them to exploit the credential enumeration flaw
-
Audit system-scoped credentialsGo to Jenkins > Manage Jenkins > Manage Credentials > System > System-wide credentials. Review if any credentials are stored there. Then test if a user with only Job/Configure permission can access credential IDs by making HTTP requests to the Config File Provider plugin endpointsAffected if System-scoped credentials exist and users with limited permissions can enumerate their IDs through the vulnerable plugin endpoints
You are affected if the Config File Provider Plugin version is 3.7.0 or earlier AND untrusted users have global Job/Configure permission, allowing them to enumerate credential IDs stored in Jenkins.
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 dataUpdate Config File Provider Plugin to version 3.7.1 or later. Restrict global Job/Configure permission to only necessary users until the patch is applied.
Fix this in Config File Provider
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing3.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,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-21643 — 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-21643 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