Buildgraph ViewApplication · Jenkins
CVE-2019-16562
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 buildgraph-view Plugin 1.8 and earlier does not escape the description of builds shown in its view, resulting in a stored XSS vulnerability exploitable by users able to change build descriptions.
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 buildgraph-view Plugin versions 1.8 and earlier fails to sanitize build descriptions before rendering them in the plugin's view, allowing authenticated users with build description modification privileges to inject malicious scripts that execute in the browsers of other users viewing the buildgraph.
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
Buildgraph ViewApplication
<= 1.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 buildgraph-view plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'buildgraph-view', or check the $JENKINS_HOME/plugins directory for the buildgraph-view plugin folderAffected if the buildgraph-view plugin is not found in the plugin list, the vulnerability does not apply
-
Determine installed plugin versionIn Manage Jenkins > Manage Plugins > Installed tab, find buildgraph-view and note the version number displayed in the 'Version' columnAffected if the installed version is 1.8 or earlier (such as 1.7, 1.6, etc.)
-
Check if plugin is actually usedReview Jenkins jobs to see if any use the buildgraph-view column or view. Look for jobs that include the buildgraph-view column in their configuration or have a buildgraph view configuredAffected if the plugin is installed but not used in any job configuration, the XSS risk is reduced but the vulnerability still exists in the plugin code
-
Identify users with build description permissionNavigate to Manage Jenkins > Manage Users and review which users have the 'Edit Build Description' permission. Check job-level permissions in Configure > Authorization sections of individual jobsAffected if any authenticated user account exists with permission to modify build descriptions, the XSS vulnerability can be exploited
A user is affected if the buildgraph-view plugin version 1.8 or earlier is installed and any user has permission to modify build descriptions in Jenkins.
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 buildgraph-view plugin to version 1.9 or later which includes proper output encoding of build descriptions. Until updated, restrict or monitor which users can modify build descriptions.
Fix this in Buildgraph View
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-2019-16562 — 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-16562 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