dbcve.org
NunitApplication · Jenkins

CVE-2022-43414

MEDIUM · 5.3 CVSS v3.1 Published 2022-10-19
Fix available
A fix is available. Upgrade to 0.28 or later.
See remediation →
62/100
Remediation priority · Elevated
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 NUnit Plugin 0.27 and earlier implements an agent-to-controller message that parses files inside a user-specified directory as test results, allowing attackers able to control agent processes to obtain test results from files in an attacker-specified directory on the Jenkins controller.

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 NUnit Plugin versions 0.27 and earlier contains a path traversal vulnerability in its agent-to-controller message functionality. Attackers who can control agent processes can specify an arbitrary directory path on the Jenkins controller, causing the plugin to parse files from that location as test results and exfiltrate their contents.

MitigationUpgrade the NUnit Plugin to version 0.28 or later, which includes a fix for the path traversal vulnerability. Additionally, restrict agent-to-controller messaging permissions and monitor for unusual directory 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
NunitApplication
Affected:< 0.28

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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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. Verify NUnit Plugin is installed
    Navigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab and search for 'NUnit' in the filter, or run: jenkins-cli.jar get-plugins (or check $JENKINS_HOME/plugins for nunit.hpi)
    Affected if The NUnit plugin appears in the installed plugins list
  2. Determine installed NUnit Plugin version
    In Jenkins UI: Manage Jenkins > Manage Plugins > Installed > NUnit > Version column. Or inspect the plugin's manifest:打开 $JENKINS_HOME/plugins/nunit/WEB-INF/manifest.json or the .hpi file's MANIFEST.MF
    Affected if The version number is less than 0.28 (for example: 0.27, 0.26, etc.)
  3. Confirm agent-to-controller messaging is in use
    Review Jenkins configuration for any pipelines or jobs that use the NUnit plugin in conjunction with agents (distributed builds). Check job configurations for 'NUnit' publisher step combined with agent-based executors.
    Affected if The NUnit plugin is used in jobs that run on agent nodes; however, any installation of a vulnerable version (< 0.28) with the plugin enabled is potentially affected if agents can be compromised

The environment is affected if the installed NUnit Plugin version is 0.27 or earlier, regardless of whether agent-to-controller messaging is actively configured, since the vulnerability exists in the plugin's core functionality.

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 0.28 or later
Fixed in 0.28
Interim mitigation

Upgrade the NUnit Plugin to version 0.28 or later, which includes a fix for the path traversal vulnerability. Additionally, restrict agent-to-controller messaging permissions and monitor for unusual directory access patterns.

Recommended fix High confidence

NUnit Plugin version 0.28 or later

  1. 1. In the Jenkins controller web UI, navigate to 'Manage Jenkins'
  2. 2. Click on 'Manage Plugins'
  3. 3. Select the 'Updates' tab
  4. 4. Locate the 'NUnit' plugin in the list
  5. 5. Check the checkbox next to NUnit plugin
  6. 6. Click 'Download now and install after restart' or 'Update' button
  7. 7. Wait for the plugin to download and install
  8. 8. Restart Jenkins to complete the upgrade

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

Fix this in Nunit Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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