Owasp Dependency TrackApplication · Jenkins
CVE-2021-21632
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 missing permission check in Jenkins OWASP Dependency-Track Plugin 3.1.0 and earlier allows attackers with Overall/Read permission to connect to an attacker-specified URL, capturing 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 · high confidenceMissing permission check in Jenkins OWASP Dependency-Track Plugin 3.1.0 and earlier allows attackers with Overall/Read permission (lowest privilege) to make the Jenkins instance connect to an attacker-controlled URL, enabling credential capture through the affected plugin's integration with stored Jenkins credentials.
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
Owasp Dependency TrackApplication
<= 3.1.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 OWASP Dependency-Track Plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed, or use the Jenkins script console with: Jenkins.instance.pluginManager.plugins.findAll { it.shortName == 'dependency-track-plugin' }Affected if The plugin appears in the installed plugins list
-
Check the installed plugin versionIn Manage Jenkins > Manage Plugins > Installed, locate OWASP Dependency-Track and note the Version column, or inspect the plugin's manifest file (META-INF/MANIFEST.MF) in the plugin's .hpi fileAffected if The version listed is 3.1.0 or any version lower (e.g., 3.0.0, 2.x, 1.x)
-
Confirm credentials are configured for the pluginNavigate to Manage Jenkins > Manage Credentials, or check the plugin's configuration under Manage Jenkins > Configure System (look for OWASP Dependency-Track settings) to see if any API keys, tokens, or credentials are storedAffected if Any Jenkins credentials are stored and associated with the OWASP Dependency-Track plugin configuration
-
Verify the plugin configuration includes a Dependency-Track server URLCheck the plugin's global configuration (usually under Manage Jenkins > Configure System > OWASP Dependency-Track) to see if a server URL is definedAffected if A Dependency-Track server URL is configured, as this is the connection point that could be redirected to an attacker-controlled server
You are affected if the OWASP Dependency-Track Plugin is installed at version 3.1.0 or earlier AND has credentials or a server URL configured, allowing an attacker with basic read access to trigger connections to malicious URLs.
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 OWASP Dependency-Track Plugin to version 3.1.1 or later; if no patched version exists, disable or remove the plugin and rotate any credentials that may have been exposed through the vulnerable plugin.
Fix this in Owasp Dependency Track
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2021-21632 — 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-21632 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