Groovy PostbuildApplication · Jenkins
CVE-2018-1000202
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 Groovy Postbuild Plugin 2.3.1 and older in various Jelly files 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 stored cross-site scripting vulnerability in Jenkins Groovy Postbuild Plugin 2.3.1 and older allows attackers with control over build badge content to inject malicious JavaScript that executes in other users' browsers when they perform certain UI actions. The vulnerability exists in multiple Jelly view files that fail to properly sanitize user-controlled build badge content before rendering.
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
Groovy PostbuildApplication
<= 2.3.1CVSS 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 is runningAccess Jenkins web UI or check Jenkins process is activeAffected if Jenkins instance is running with the Groovy Postbuild plugin installed
-
Locate the Groovy Postbuild PluginNavigate to Manage Jenkins > Manage Plugins > Installed tab and find 'Groovy Postbuild' in the listAffected if Plugin is installed on the Jenkins instance
-
Check installed plugin versionIn the plugin list, note the version number displayed for Groovy Postbuild PluginAffected if Version is 2.3.1 or older (any version <= 2.3.1)
-
Identify Jelly view files in the pluginLocate the plugin JAR/WAR file (typically in $JENKINS_HOME/plugins/groovy-postbuild/ or /var/lib/jenkins/plugins/groovy-postbuild/) and examine the Jelly view files in the views directoryAffected if The Jelly files do not contain proper sanitization of build badge content before rendering
-
Determine if build badge feature is in useReview Jenkins job configurations and build logs for usage of the build badge API or postbuild groovy scripts that set build badge contentAffected if Build badge content is being set or controlled through job configurations or build scripts
You are affected if Jenkins is running with Groovy Postbuild Plugin version 2.3.1 or older AND the build badge feature is being used to display content in build views.
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 the Groovy Postbuild Plugin to version 2.3.2 or later, which contains proper sanitization of build badge content in the affected Jelly files.
Fix this in Groovy Postbuild
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-1000202 — 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-1000202 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