Skip to content

← Public intelligence

Maven package

com.zaxxer:nuprocess

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. High, CVSS 8.4MavenPublished

    NuProcess vulnerable to command-line injection through insertion of NUL character(s)

    CVE-2022-39243 · GHSA-cxgf-v2p8-7ph7

    Affected
    • Maven com.zaxxer:nuprocess >= 1.2.0, < 2.0.5
    Fixed in
    2.0.5· Vendor fix available
    Issue
    Impact In all the versions of NuProcess where it forks processes by using the JVM's JavajavalangUNIXProcessforkAndExec 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. - On macOS, any argument with a NUL character is truncated at that character. This means the malicious arguments are never seen by the started process. - On Windows, the entire command line is truncated at the first NUL character. This means the malicious arguments, and any intentional arguments provided after them, are never seen by the started process. Patches 2.0.5 Workarounds Users of the library can sanitize command strings to remove NUL characters prior to passing them to NuProcess for execution. References None.

    Recommended action: Upgrade to 2.0.5 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →