CliInvoke
Affected
- introduced
2.0.0, fixed2.8.5(ecosystem)
Fixed versions
2.8.5
Fix
The export has no generic command for this ecosystem.
Advisory
Also known as: CVE-2026-100369
CliInvoke: Argument Injection in Extensibility Runner Factory
Impact
An argument-injection vulnerability exists in the CliInvoke
package's runner factory: RunnerProcessFactory on the 2.x line andRunnerConfigurationFactory 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:
Workarounds
No complete workaround is available. Until you can upgrade:
" from any target or argument before passing it to the factory. On shell runners, also strip ;, |, &, $, backtick, and parentheses.ProcessConfiguration directly. Set ArgumentList explicitly to the argv you want the runner to receive.These are partial mitigations. They shift the quoting problem to your
code.
High Basis: The source's own band: HIGH
2.0.0, fixed 2.8.5 (ecosystem)2.8.5
The export has no generic command for this ecosystem.
2.9.0, fixed 2.9.4 (ecosystem)2.9.4
The export has no generic command for this ecosystem.
2.10.0, fixed 2.10.5 (ecosystem)2.10.5
The export has no generic command for this ecosystem.
3.0.0-alpha.1, fixed 3.0.0-beta.2 (ecosystem)3.0.0-beta.2
The export has no generic command for this ecosystem.
2.0.0-alpha.1, fixed 2.0.2 (ecosystem)2.0.2
The export has no generic command for this ecosystem.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0