dbcve.org
XunitApplication · Jenkins

CVE-2022-34181

CRITICAL · 9.1 CVSS v3.1 Published 2022-06-23
Fix available
A fix is available. Upgrade to after 3.0.8 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 xUnit Plugin 3.0.8 and earlier implements an agent-to-controller message that creates a user-specified directory if it doesn't exist, and parsing files inside it as test results, allowing attackers able to control agent processes to create an arbitrary directory on the Jenkins controller or to obtain test results from existing files in an attacker-specified directory.

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 xUnit Plugin versions 3.0.8 and earlier has a critical vulnerability where an agent-to-controller message allows creation of user-specified directories and parsing of files within them as test results. Attackers who can control agent processes can exploit this to create arbitrary directories on the Jenkins controller or read existing files (test results) from any attacker-specified directory, effectively enabling path traversal and arbitrary file read on the controller.

MitigationUpgrade xUnit Plugin to version 3.1.0 or later which implements proper input validation on directory paths. If upgrading is not immediately possible, restrict agent process control to trusted sources and monitor for unusual directory creation or file access patterns.

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
XunitApplication
Affected:<= 3.0.8

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 installed xUnit plugin version
    Navigate to Manage Jenkins > Manage Plugins > Installed tab, locate xUnit Plugin in the list, and note the Version column. Alternatively, access $JENKINS_HOME/plugins/xunit/WEB-INF/lib/xunit.hpi (or .jpi) META-INF/MANIFEST.MF to read the Plugin-Version attribute.
    Affected if The installed version is 3.0.8 or earlier (any version listed as <= 3.0.8).
  2. Confirm xUnit plugin is enabled
    In Manage Jenkins > Manage Plugins > Installed tab, verify that xUnit Plugin shows as Enabled (the checkbox is checked) and not disabled or pending restart.
    Affected if The plugin is installed AND enabled (the vulnerability only applies when the plugin is active).
  3. Review connected agent configurations
    Navigate to Manage Jenkins > Manage Nodes. Examine each agent's configuration, particularly any agents launched via inbound agents (JNLP) or agents where the launch method allows external control.
    Affected if Any agent with a launch method that permits external/untrusted process control (such as inbound JNLP agents from untrusted sources, or agents configured with arbitrary command execution).
  4. Inspect recent test result parsing activity
    Review Jenkins build logs and the $JENKINS_HOME/jobs/*/builds/*/xunit.xml files or console output for entries indicating xUnit result parsing. Look for test result submissions from agent nodes.
    Affected if Test results have been processed via the xUnit plugin from agent-bound jobs, especially where the test result path is user-controllable.

You are affected if the xUnit plugin version is 3.0.8 or earlier AND the plugin is enabled AND you have agents that could be controlled by untrusted parties submitting test results through the xUnit plugin.

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 3.0.8
Interim mitigation

Upgrade xUnit Plugin to version 3.1.0 or later which implements proper input validation on directory paths. If upgrading is not immediately possible, restrict agent process control to trusted sources and monitor for unusual directory creation or file access patterns.

Recommended fix High confidence

xUnit Plugin version 3.1 or later

  1. 1. Navigate to the Jenkins dashboard
  2. 2. Go to 'Manage Jenkins' > 'Manage Plugins'
  3. 3. Click on the 'Installed' tab
  4. 4. Search for 'xUnit Plugin' in the plugin list
  5. 5. If the installed version is 3.0.8 or earlier, click 'Update' to upgrade to the latest version
  6. 6. After the update completes, restart Jenkins to apply the changes
  7. 7. Alternatively, download the updated .hpi file from the Jenkins plugin repository and install it via 'Manage Plugins' > 'Advanced' > 'Upload Plugin'

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

Fix this in Xunit Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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