JenkinsApplication
CVE-2022-34172
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 · uneditedIn Jenkins 2.340 through 2.355 (both inclusive) symbol-based icons unescape previously escaped values of 'tooltip' parameters, resulting in a cross-site scripting (XSS) vulnerability.
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 confidenceJenkins versions 2.340 through 2.355 contain a cross-site scripting (XSS) vulnerability where symbol-based icons improperly unescape previously escaped values in 'tooltip' parameters, allowing attackers to inject malicious scripts through crafted tooltip content.
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
JenkinsApplication
>= 2.340, <= 2.355CVSS 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.
-
Check installed Jenkins versionNavigate to Manage Jenkins > About Jenkins or run 'java -jar jenkins.war --version' from the server consoleAffected if The reported version is 2.340, 2.341, 2.342, 2.343, 2.344, 2.345, 2.346, 2.347, 2.348, 2.349, 2.350, 2.351, 2.352, 2.353, 2.354, or 2.355
-
Identify use of symbol-based icons with tooltipsSearch Jenkins configuration files, job definitions, and user-created UI elements for usage of the symbol icon syntax (typically defined via Jenkins shared libraries or plugins that support symbol-based icons) combined with tooltip parametersAffected if Symbol-based icons with tooltip parameters are present in the environment and the Jenkins version falls within the affected range
The environment is affected if the installed Jenkins version is between 2.340 and 2.355 inclusive and symbol-based icons with tooltip parameters are in use.
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.
dbcve · scopedUpgrade Jenkins to version 2.356 or later. As a temporary workaround, avoid using symbol-based icons with user-controlled tooltip values until the upgrade can be applied.
Jenkins 2.356 or later (LTS 2.361.1+ recommended)
- Check current Jenkins version via Manage Jenkins > About Jenkins
- Back up Jenkins home directory ($JENKINS_HOME) and configuration
- Schedule a maintenance window as Jenkins will restart during upgrade
- Download and install Jenkins 2.356 or later (or LTS 2.361.1+)
- Restart Jenkins to apply the upgrade
- Verify new version is running via Manage Jenkins > About Jenkins
- Confirm the tooltip XSS vulnerability is fixed by testing symbol-based icons with tooltip parameters
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Jenkins
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-2022-34172 — 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-34172 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