Dashboard ViewApplication · Jenkins
CVE-2019-10396
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 Dashboard View Plugin 2.11 and earlier did not escape build descriptions, resulting in a cross-site scripting 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 Dashboard View Plugin versions 2.11 and earlier fails to properly escape build descriptions before rendering them in the dashboard view, allowing authenticated users with permission to modify build descriptions to inject arbitrary JavaScript that executes in the browsers of other users viewing the dashboard.
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
Dashboard ViewApplication
<= 2.11CVSS 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 Dashboard View Plugin is installedNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab and search for 'Dashboard View', or inspect the plugin directory (typically $JENKINS_HOME/plugins/dashboard-view*).Affected if Plugin is present in the plugin list or filesystem.
-
Determine installed plugin versionIn Manage Jenkins > Manage Plugins > Installed tab, find Dashboard View and note the version column; alternatively, check the plugin's MANIFEST.MF file in $JENKINS_HOME/plugins/dashboard-view/.Affected if Version is 2.11 or earlier.
-
Identify active dashboard viewsGo to the Jenkins home page and look for any views named 'Dashboard', 'Dashboard View', or custom dashboards. Check the main view configuration at Jenkins > Manage Jenkins > Configure System for Dashboard View settings.Affected if Any dashboard views created with this plugin are visible or configured.
-
Confirm build descriptions are displayed on dashboardsOpen an active dashboard view and inspect whether build descriptions (set via build configuration or builds > configure > description) appear in the dashboard panels. Check the dashboard configuration for 'Build Description' or similar widgets.Affected if Build descriptions from builds are rendered on any dashboard view.
User is affected if Dashboard View Plugin version 2.11 or earlier is installed AND active dashboard views display build descriptions from builds.
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 Dashboard View Plugin to version 2.12 or later which includes proper HTML escaping for build descriptions. Alternatively, restrict the permission to configure builds to trusted users only until the upgrade can be applied.
Fix this in Dashboard View
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10396 — 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-10396 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