# CVE-2022-39243: NuProcess vulnerable to command-line injection through insertion of NUL character(s)

> Attackers can inject command-line arguments via NUL characters in NuProcess, potentially leading to code execution on Linux systems.

- **Severity:** High 8.4 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Sep 2022
- **Updated:** 22 Apr 2025
- **Also known as:** GHSA-cxgf-v2p8-7ph7, UBUNTU-CVE-2022-39243

## What is CVE-2022-39243?

CVE-2022-39243 is a high-severity command injection vulnerability in brettwooldridge NuProcess, published on 26 Sep 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

NuProcess is an external process execution implementation for Java. In all the versions of NuProcess where it forks processes by using the JVM's Java_java_lang_UNIXProcess_forkAndExec method (1.2.0+), attackers can use NUL characters in their strings to perform command line injection. Java's ProcessBuilder isn't vulnerable because of a check in ProcessBuilder.start. NuProcess is missing that check. This vulnerability can only be exploited to inject command line arguments on Linux. Version 2.0.5 contains a patch. As a workaround, users of the library can sanitize command strings to remove NUL characters prior to passing them to NuProcess for execution.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

## Which versions are affected by CVE-2022-39243?

2 open source packages ship an affected version, including com.zaxxer:nuprocess. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `com.zaxxer:nuprocess` | Maven | From 1.2.0 | 2.0.5 |
| `com.zaxxer:nuprocess` | Maven | From 1.2.0 | 2.0.5 |

Products: Nuprocess Project Nuprocess.

## How do I fix CVE-2022-39243?

Upgrade com.zaxxer:nuprocess to 2.0.5 or later.

## Is CVE-2022-39243 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-39243 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-39243 and fix it if it is affected.

What it is: CVE-2022-39243 is a high-severity command injection vulnerability in brettwooldridge NuProcess, published on 26 Sep 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-39243 exists.

Affected packages and fixed versions:
- com.zaxxer:nuprocess (Maven): affected from 1.2.0; fixed in 2.0.5
- com.zaxxer:nuprocess (Maven): affected from 1.2.0; fixed in 2.0.5

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-39243/ (Markdown: https://insights.sbomify.com/CVE-2022-39243/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-39243
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-39243
- OSV: https://osv.dev/vulnerability/CVE-2022-39243

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-39243/
Summaries are generated and may contain mistakes; the official description above is the record.