Deployment DashboardApplication · Jenkins
CVE-2022-34795
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 Deployment Dashboard Plugin 1.0.10 and earlier does not escape environment names on its Deployment Dashboard view, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers with View/Configure permission.
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 Deployment Dashboard Plugin versions 1.0.10 and earlier fails to properly escape environment names when rendering the Deployment Dashboard view. An attacker with View/Configure permission can inject malicious JavaScript code into environment names, which executes when other users view the dashboard—a classic stored XSS vulnerability.
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
Deployment DashboardApplication
<= 1.0.10CVSS 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 Deployment Dashboard Plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'Deployment Dashboard' in the list of installed plugins.Affected if The plugin appears in the installed plugins list.
-
Check the installed plugin versionIn the Installed Plugins list, locate the Deployment Dashboard Plugin and note the Version column. Compare this version number to 1.0.10.Affected if The installed version is 1.0.10 or lower.
-
Identify users with View/Configure permissionNavigate to Manage Jenkins > Manage Users and/or check Matrix-based security settings under Manage Jenkins > Configure Global Security to see which users or groups have View/Configure or Overall/Read with Job/Configure permissions.Affected if Users with View/Configure permissions include accounts that are not fully trusted or are outside your security perimeter.
-
Inspect configured environment names for suspicious contentAccess the Deployment Dashboard view (typically at /plugin/deployment-dashboard/ or via a job's dashboard link) and review all environment names listed. Look for unusual characters, script tags, or encoded content that may indicate injected code.Affected if Any environment name contains <script>, javascript:, onerror=, or other HTML/JavaScript syntax.
-
Check if the dashboard view is accessible to other usersVerify that the Deployment Dashboard is visible to multiple users by checking who can access the Jenkins main page or specific job views that include the dashboard.Affected if Multiple users can view the dashboard and the plugin is enabled on any jobs.
You are affected if the Deployment Dashboard Plugin version is 1.0.10 or earlier AND untrusted users have View/Configure permission to inject environment names that would execute when viewed by others.
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 Jenkins Deployment Dashboard Plugin. Until patched, limit or audit users with View/Configure permissions to trusted personnel only.
Fix this in Deployment Dashboard
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-34795 — 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-2022-34795 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