Build PipelineApplication · Jenkins
CVE-2019-10373
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 stored cross-site scripting vulnerability in Jenkins Build Pipeline Plugin 1.5.8 and earlier allows attackers able to edit the build pipeline description to inject arbitrary HTML and JavaScript in the plugin-provided web pages 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 confidenceThis is a stored cross-site scripting (XSS) vulnerability in the Jenkins Build Pipeline Plugin version 1.5.8 and earlier. Attackers with permission to edit build pipeline descriptions can inject arbitrary HTML and JavaScript code that gets persistently stored and executed in the browsers of other users who view the affected plugin-provided web pages.
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
Build PipelineApplication
<= 1.5.8CVSS 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.
-
Verify Build Pipeline Plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'Build Pipeline' in the list, or use the Jenkins CLI: java -jar jenkins-cli.jar -s http://localhost:8080/ list-plugins | grep -i pipelineAffected if The Build Pipeline Plugin appears in the installed plugins list
-
Identify the installed versionIn the Installed Plugins tab, locate the 'Build Pipeline' plugin and read the Version column, or query via API: curl -s http://localhost:8080/pluginManager/plugin/build-pipeline-plugin/api/json?tree=versionAffected if The version is 1.5.8 or earlier (e.g., 1.5.8, 1.5.7, 1.5.6, etc.)
-
Confirm plugin is active and not disabledIn Manage Plugins > Installed, verify the 'Enable' checkbox is checked for the Build Pipeline Plugin, or check that the plugin appears in the active plugins list via APIAffected if The plugin is enabled and loaded into Jenkins runtime
-
Check for existing pipeline descriptions with injected codeNavigate to each Build Pipeline view, inspect the pipeline configuration, and review the Description field for suspicious HTML tags (script, iframe, img onerror) or JavaScript code; alternatively, search job configurations via: curl -s http://localhost:8080/api/json?tree=jobs[name,description] | grep -i '<script\|javascript\|onerror\|onload'Affected if Any pipeline description contains unescaped HTML markup or JavaScript that could execute in a browser
A user is affected if the Build Pipeline Plugin is installed and enabled with version 1.5.8 or earlier, regardless of whether malicious descriptions are currently present.
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 the Build Pipeline Plugin to a version newer than 1.5.8. Additionally, review and restrict user permissions for editing build pipeline descriptions to minimize the attack surface.
Fix this in Build Pipeline
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10373 — 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-2019-10373 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