Pipeline Aggregator ViewApplication · Jenkins
CVE-2019-16564
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 Pipeline Aggregator View Plugin 1.8 and earlier does not escape information shown on its view, resulting in a stored XSS vulnerability exploitable by attackers able to affects view content such as job display name or pipeline stage names.
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 Pipeline Aggregator View Plugin versions 1.8 and earlier fails to properly escape content displayed in its view interface. This stored XSS vulnerability allows attackers who can influence job display names or pipeline stage names to inject malicious scripts that execute in the browsers of users viewing the affected pipeline aggregates.
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
Pipeline Aggregator 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.
-
Confirm Pipeline Aggregator View Plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'Pipeline Aggregator View', or inspect $JENKINS_HOME/plugins for the pipeline-aggregator-view directoryAffected if Plugin is present on the Jenkins instance
-
Determine installed plugin versionLocate the plugin's manifest file at $JENKINS_HOME/plugins/pipeline-aggregator-view/META-INF/MANIFEST.MF and read the Implementation-Version attributeAffected if Version is 1.8 or earlier
-
Identify views using the pluginCheck Jenkins view configurations in $JENKINS_HOME/users/*/config.xml or browse to /view/All/ on the web UI to see if any views list 'Pipeline Aggregator View' as their typeAffected if Any view is configured to use the Pipeline Aggregator View plugin
-
Review job display names for injected contentSearch job config.xml files in $JENKINS_HOME/jobs/*/config.xml for <displayName> elements containing HTML tags, script elements, or event handlers like onload, onerror, onclickAffected if Any job display names contain unescaped HTML or JavaScript content
-
Inspect pipeline stage names for XSS vectorsReview Jenkinsfile definitions or job configurations for stage blocks with names that may contain HTML or script contentAffected if Pipeline stage names contain unescaped HTML or JavaScript content
The environment is affected if the Pipeline Aggregator View plugin version 1.8 or earlier is installed, any views use this plugin, and job display names or pipeline stage names contain unescaped HTML or script content that could be executed in user browsers.
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 to a patched version of the Pipeline Aggregator View Plugin that implements proper output encoding, or if no patch exists, restrict administrative access to job and stage naming to prevent injection of malicious content.
Fix this in Pipeline Aggregator View
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-16564 — 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-16564 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