dbcve.org
JenkinsApplication

CVE-2022-34173

MEDIUM · 5.4 CVSS v3.1 Published 2022-06-23
Fix available
A fix is available. Upgrade to after 2.355 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
In Jenkins 2.340 through 2.355 (both inclusive) the tooltip of the build button in list views supports HTML without escaping the job display name, resulting in a cross-site scripting (XSS) vulnerability exploitable by attackers with Job/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 confidence

This is a stored XSS vulnerability in Jenkins where the tooltip of the build button in list views renders HTML without escaping the job display name. Attackers with Job/Configure permission can inject malicious HTML/JavaScript into a job's display name, which will execute in the browsers of other users viewing the list.

MitigationUpgrade Jenkins to version 2.356 or later, which contains the fix for proper HTML escaping of the job display name in the build button tooltip.

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
Affected:>= 2.340, <= 2.355

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check your Jenkins version
    Navigate to Manage Jenkins > About Jenkins, or access /whoAmI/ or use: java -jar jenkins-cli.jar who-am-i (if available). The version is displayed on the main dashboard footer or the About page.
    Affected if The version shown is 2.340 through 2.355 inclusive.
  2. Identify custom job display names
    Review jobs in list views for any that have custom display names different from their job folder/folder name. Check each job's configuration under 'Display Name' field in the General section.
    Affected if Any job has a Display Name set that contains HTML tags such as <script>, <img>, <iframe>, or other HTML/JavaScript.
  3. Inspect list view build button tooltips
    Hover over the 'Build' button (play icon) next to jobs in any list view. Observe if the tooltip renders HTML or executes JavaScript rather than showing plain text.
    Affected if The tooltip displays formatted HTML, executes script, or behaves unexpectedly beyond plain text rendering.
  4. Verify Job/Configure permissions
    Review which users or groups have Job/Configure or Overall/Administer permissions in Manage Jenkins > Manage Users and Manage Jenkins > Security.
    Affected if Untrusted users have Job/Configure permission and could inject malicious display names.

You are affected if running Jenkins version 2.340-2.355 AND an untrusted user with Job/Configure permission has set a display name containing HTML/JavaScript that renders in the build button tooltip.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 2.355
Interim mitigation

Upgrade Jenkins to version 2.356 or later, which contains the fix for proper HTML escaping of the job display name in the build button tooltip.

Recommended fix High confidence

Jenkins 2.356 (weekly) or Jenkins 2.346.2 LTS (or later in both tracks)

  1. 1. Back up your Jenkins home directory (JENKINS_HOME) including all configurations, jobs, and plugins
  2. 2. Review plugin compatibility with the target Jenkins version before upgrading
  3. 3. Download Jenkins 2.356 or later (weekly release), or Jenkins 2.346.2+ (LTS release) from https://www.jenkins.io/download/
  4. 4. Stop the Jenkins service
  5. 5. Replace the Jenkins WAR file (jenkins.war) with the new version
  6. 6. Start the Jenkins service
  7. 7. Verify the upgrade by logging into the Jenkins web interface
  8. 8. Confirm that jobs and pipelines are functioning correctly
Caveat Review plugin compatibility before upgrading; some older plugins may require updates for newer Jenkins versions

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
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-34173 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-34173 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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