BadgeApplication · Jenkins
CVE-2018-1000604
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 persisted cross-site scripting vulnerability exists in Jenkins Badge Plugin 1.4 and earlier in BadgeSummaryAction.java, HtmlBadgeAction.java that allows attackers able to control build badge content to define JavaScript that would be executed in another user's browser when that other user performs some UI actions.
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 confidenceA persisted cross-site scripting (XSS) vulnerability in Jenkins Badge Plugin 1.4 and earlier allows attackers who can control build badge content to inject malicious JavaScript that executes in other users' browsers when they interact with the badge UI components BadgeSummaryAction.java and HtmlBadgeAction.java.
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
BadgeApplication
<= 1.4CVSS 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.0/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.
-
Verify Jenkins Badge Plugin is installedAccess Jenkins UI, go to Manage Jenkins > Manage Plugins > Installed tab, or inspect $JENKINS_HOME/plugins/ directory for a folder named 'badge'Affected if The badge plugin folder exists in the plugins directory or is listed in the Jenkins plugin manager
-
Determine the installed plugin versionIn Jenkins UI, find the Badge Plugin in the Installed plugins list and note the version number shown, or inspect the manifest file at $JENKINS_HOME/plugins/badge/MANIFEST.MFAffected if The version number is 1.4 or lower, or the manifest shows a version <= 1.4
-
Identify if build badge functionality is accessibleCheck if the Jenkins user has access to add or modify build badges through job configuration or build actions; look for BadgeSummaryAction or HtmlBadgeAction endpoints under /jenkins/badge/ paths in web requestsAffected if Users can add custom text or images to build badges without restricted permissions, or the badge action URLs are accessible
-
Check for existing malicious badge contentReview recent build records via Jenkins UI or API for any badge entries that contain suspicious HTML, script tags, or javascript: URIs in the badge text fieldsAffected if Any build records display badge content with unescaped HTML or script tags when viewed in the browser
You are affected if the Jenkins Badge Plugin version is 1.4 or earlier AND users have the ability to add or modify build badges, allowing injection of unsanitized content that persists across build interactions.
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 Jenkins Badge Plugin to version 1.5 or later which includes proper input sanitization/escaping of badge content, or implement output encoding in the affected Java files to prevent script execution.
Fix this in Badge
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-1000604 — 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-2018-1000604 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