dbcve.org
JenkinsApplication

CVE-2022-34170

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.320 through 2.355 (both inclusive) and LTS 2.332.1 through LTS 2.332.3 (both inclusive) the help icon does not escape the feature name that is part of its tooltip, effectively undoing the fix for SECURITY-1955, 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

In Jenkins 2.320-2.355 and LTS 2.332.1-2.332.3, the help icon tooltip fails to properly escape the feature name, creating a stored XSS vulnerability. Attackers with Job/Configure permission can inject malicious JavaScript into the feature name which executes when other users hover over the help icon, effectively undoing the previous fix from SECURITY-1955.

MitigationUpgrade Jenkins to version 2.356 or later, or LTS 2.332.4 or later, which properly escape the feature name in the help icon 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.320, <= 2.355>= 2.332.1, <= 2.332.3

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 the Jenkins version displayed in the UI
    Scroll to the bottom of any Jenkins page - the version is shown in the footer. Alternatively, go to Manage Jenkins > About Jenkins to see the exact version number.
    Affected if The displayed version is 2.320 through 2.355, or 2.332.1 through 2.332.3
  2. Verify the version via the API
    Access the URL /api/json?tree=version or /api/xml?tree=version on your Jenkins server. The JSON or XML response will contain the exact version field.
    Affected if The version field matches any of the following ranges: 2.320 <= version <= 2.355, or 2.332.1 <= version <= 2.332.3
  3. Check CLI or startup logs for version
    If you have shell access, run 'java -jar jenkins.war --version' if you have the war file, or check the startup logs. The version is printed at startup and visible in the log files.
    Affected if The reported version falls within the affected ranges listed above

You are affected if your Jenkins version is 2.320-2.355 or 2.332.1-2.332.3; the stored XSS can then be triggered if an attacker with Job/Configure permission injects malicious script into a feature name.

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, or LTS 2.332.4 or later, which properly escape the feature name in the help icon tooltip.

Recommended fix High confidence

Jenkins weekly 2.356+ or Jenkins LTS 2.332.4+

  1. Identify your current Jenkins version by navigating to Manage Jenkins > About Jenkins
  2. If running Jenkins weekly between 2.320 and 2.355 inclusive, upgrade to Jenkins 2.356 or later
  3. If running Jenkins LTS between 2.332.1 and 2.332.3 inclusive, upgrade to Jenkins LTS 2.332.4 or later
  4. Download the appropriate WAR file from https://www.jenkins.io/download/
  5. Stop the Jenkins service
  6. Replace the existing jenkins.war file with the new version
  7. Start the Jenkins service
  8. Verify the upgrade was successful by checking Manage Jenkins > About Jenkins

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Jenkins Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-34170 — 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-34170 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