Know every vulnerabilitybefore it knows you.
DevGuard continuously monitors your dependencies and alerts you when CVEs like this one affect your stack — with real-time threat intelligence built for developers.
GHSA-j73w-8hfr-4gc9
CliInvokeCliInvokeCliInvokeImpact
An argument-injection vulnerability exists in the CliInvoke
package's runner factory: RunnerProcessFactory on the 2.x line and
RunnerConfigurationFactory on the 3.x line.
The factory joins the runner arguments, the caller's target, and the
caller's arguments into a single ProcessStartInfo.Arguments string and
hands it to the OS. The OS command-line parser re-tokenizes the string
before the runner sees it. A double quote (") in the target or in any
argument closes the OS-level quoted region and lets the next character
enter argv as a separate element.
Patches
Upgrade to:
- 2.8.5 (2.8.x line)
- 2.9.4 (2.9.x line)
- 2.10.5 (2.10.x line)
- 3.0.0-beta.2 (3.x pre-release line)
Workarounds
No complete workaround is available. Until you can upgrade:
- Strip
"from any target or argument before passing it to the factory. On shell runners, also strip;,|,&,$, backtick, and parentheses. - Or bypass the factory entirely and build the
ProcessConfigurationdirectly. SetArgumentListexplicitly to the argv you want the runner to receive.
These are partial mitigations. They shift the quoting problem to your code.
Upload your own SBOM in CycloneDX 1.6 or higher (JSON) directly here to check your vulnerabilities.
Drag and drop some file here, or click to select
The vulnerability requires local access to the device to be exploited. It is easy for an attacker to exploit this vulnerability. An attacker does not need any special privileges or access rights. No user interaction is needed for the attacker to exploit this vulnerability. The impact is confined to the system where the vulnerability exists. There is a high impact on the confidentiality of the information. There is a high impact on the integrity of the data. There is a high impact on the availability of the system.
Exploitation activity has been observed. Apply available patches or mitigations urgently.
The exploit probability is very low. The vulnerability is unlikely to be exploited in the next 30 days.
We did not find any exploit available. Neither in GitHub repositories nor in the Exploit-Database.
Browse More
Continuously monitor your dependencies and get alerted when vulnerabilities like this one affect your stack.
Checkout DevGuard