dbcve.org
JunitApplication · Jenkins

CVE-2022-34176

MEDIUM · 5.4 CVSS v3.1 Published 2022-06-23
Fix available
A fix is available. Upgrade to after 1119.va_a_5e9068da_d7 or later.
See remediation →
58/100
Remediation priority · Elevated
High EPSS 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
Jenkins JUnit Plugin 1119.va_a_5e9068da_d7 and earlier does not escape descriptions of test results, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers with Run/Update 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

The Jenkins JUnit Plugin fails to escape descriptions of test results before rendering them in the UI, allowing stored XSS attacks. Attackers with Run/Update permission can inject malicious JavaScript into test result descriptions that will execute when other users view the test results.

MitigationUpgrade the Jenkins JUnit Plugin to version 1120.v5a_6d8498c1a_5d or later, which properly escapes test result descriptions. As a compensating control, restrict Run/Update permission to trusted users only.

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
JunitApplication
Affected:<= 1119.va_a_5e9068da_d7

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 if JUnit plugin is installed
    Navigate to Manage Jenkins > Manage Plugins > Installed tab and look for 'JUnit' in the list of installed plugins, or use the Jenkins CLI: java -jar jenkins-cli.jar -s http://[jenkins-url] list-plugins | grep JUnit
    Affected if The JUnit plugin is not installed (not affected)
  2. Determine installed JUnit plugin version
    In the Installed plugins tab, find the JUnit plugin and note the Version column. Or use: java -jar jenkins-cli.jar -s http://[jenkins-url] list-plugins -xml | grep -A 10 '<name>junit</name>'
    Affected if Version is 1119.va_a_5e9068da_d7 or lower
  3. Verify if test result descriptions feature is used
    Check your CI/CD pipeline jobs or freestyle projects that publish JUnit test results. Look for post-build actions that 'Allow empty results' or similar description-related settings. Also inspect completed build artifacts for any manually added descriptions to test reports.
    Affected if Test result descriptions are being added to build records
  4. Review Run/Update permission assignment
    Navigate to Manage Jenkins > Manage and Assign Permissions. Check which users or groups have the 'Run' or 'Update' permission at the global or job-specific level. Review matrix-based security or project-based authorization matrix configurations.
    Affected if Users with untrusted or broad Run/Update permission have access to the Jenkins instance

You are affected if the JUnit plugin version is 1119.va_a_5e9068da_d7 or lower AND your Jenkins instance has users with Run/Update permission AND test result descriptions are being used in your builds.

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 1119.va_a_5e9068da_d7
Interim mitigation

Upgrade the Jenkins JUnit Plugin to version 1120.v5a_6d8498c1a_5d or later, which properly escapes test result descriptions. As a compensating control, restrict Run/Update permission to trusted users only.

Recommended fix Moderate confidence

Jenkins JUnit Plugin version 1119.v996a_2db_5b_4a_ or later (check Jenkins Security Advisory 2022-06-22 for exact fixed version)

  1. Navigate to Manage Jenkins > Manage Plugins > Installed tab
  2. Locate the 'JUnit' plugin in the list
  3. Check the current version - if it is 1119.va_a_5e9068da_d7 or earlier, an update is required
  4. Select the plugin and click 'Update' or install the latest available version
  5. Restart Jenkins if required for the update to take effect
Caveat Minor - plugin update with no expected breaking changes, standard Jenkins plugin upgrade

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

Fix this in Junit Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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