CodeWhale before 0.8.64 Argument Injection via git_show
Hmbown CodeWhale
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| deepseek-tui crates.io |
| No fix yet |
| deepseek-tui npm |
|
|
| codewhale-tui crates.io |
|
Hmbown CodeWhale
| Product | Affected | Fixed in |
|---|---|---|
| deepseek-tui crates.io |
| No fix yet |
| deepseek-tui npm |
|
|
| codewhale-tui crates.io |
|
|
| codewhale npm |
|
|
CodeWhale versions >= 0.3.27 and < 0.8.64 (published as deepseek-tui >= 0.3.27 and < 0.8.41 on npm and 0.3.27 through 0.8.41 on crates.io, and as codewhale / codewhale-tui >= 0.8.41 and < 0.8.64) contain an argument injection vulnerability in the git_show tool. The model-supplied rev parameter is passed unvalidated into the git show argv without an --end-of-options sentinel, so a value beginning with --output= is interpreted as a git flag. Because the tool is registered as auto-approved and advertised as read-only, an attacker (via a malicious repository combined with prompt injection) can cause an unprompted arbitrary file write at the privilege of the invoking user, targeting sensitive files such as ~/.ssh/authorized_keys, ~/.bashrc, or ~/.gitconfig. Fixed in codewhale / codewhale-tui 0.8.64 by adding rev validation; the deprecated deepseek-tui crate has no fixed release.
From the CVE record · VulnCheck
CodeWhale’s git_show tool passes a model-supplied revision to Git without validating it, allowing it to be interpreted as an option. An attacker who controls a malicious repository and uses prompt injection can cause the auto-approved tool to write files without a prompt, with the invoking user’s privileges.
Check installations of npm deepseek-tui >=0.3.27 and <0.8.41, crates.io deepseek-tui >=0.3.27 through 0.8.41, and npm codewhale or crates.io codewhale-tui >=0.8.41 and <0.8.64.