Owasp Dependency CheckApplication · Jenkins
CVE-2024-28153
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 OWASP Dependency-Check Plugin 5.4.5 and earlier does not escape vulnerability metadata from Dependency-Check reports, resulting in a stored cross-site scripting (XSS) vulnerability.
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 confidenceThe Jenkins OWASP Dependency-Check Plugin versions 5.4.5 and earlier fails to escape vulnerability metadata extracted from Dependency-Check scan reports before rendering it in the Jenkins UI. This allows stored XSS attacks where malicious JavaScript payloads embedded in scan report data persist and execute when administrators or other users view vulnerability details.
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 CheckApplication
< 5.4.6CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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.
-
Identify OWASP Dependency-Check Plugin installationNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab, or use the Jenkins CLI: jenkins-plugin-cli --list-plugins | grep -i 'dependency-check'Affected if The plugin appears in the list of installed plugins
-
Determine installed plugin versionIn Jenkins > Manage Jenkins > Manage Plugins > Installed, locate the 'OWASP Dependency-Check' plugin entry and note the version number shown in the 'Version' columnAffected if Version is 5.4.5 or earlier (any version below 5.4.6)
-
Verify plugin is configured for buildsCheck existing Jenkins jobs: navigate to a job configuration, look for the 'Invoke OWASP Dependency-Check' build step in the 'Build Steps' section, or search for 'dependency-check' in job configurations via Jenkins script consoleAffected if Any job has the Dependency-Check build step configured and enabled
If the OWASP Dependency-Check Plugin is installed at version 5.4.5 or earlier and is used in any job configuration, the environment is affected by this stored XSS vulnerability.
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.
dbcve · scoped5.4.6
Update the OWASP Dependency-Check Plugin to version 5.4.6 or later, which contains proper output escaping for vulnerability metadata. Verify that Dependency-Check scans continue to function correctly after the update.
5.4.6
- Back up your Jenkins configuration before updating any plugins
- Navigate to Manage Jenkins > Manage Plugins
- Go to the 'Available' tab and search for 'OWASP Dependency-Check Plugin'
- Update the plugin to version 5.4.6 or later
- Restart Jenkins if prompted or manually restart the Jenkins service
- Verify the plugin version has been updated to 5.4.6 or higher in the installed plugins list
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Owasp Dependency Check
Scoped from the published advisory
- Consultation1.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-28153 — 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-2024-28153 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