CodeWhale before 0.8.64 Remote Code Execution via allow_shell
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 before 0.8.64 fail to properly validate the allow_shell configuration parameter from project config files, allowing attackers to enable arbitrary shell command execution by committing a malicious .codewhale/config.toml file to a repository. When a user clones and opens the repository in CodeWhale, the AI model gains access to exec_shell and task_shell tools, enabling execution of arbitrary shell commands on the victim's machine without explicit user consent.
From the CVE record · VulnCheck
CodeWhale does not properly validate the allow_shell setting in project configuration files. An attacker can commit a malicious .codewhale/config.toml to a repository; when a user clones and opens it in CodeWhale, the AI model can execute arbitrary shell commands on the user's machine without explicit consent.
Check installations of npm deepseek-tui >=0.8.6 and <0.8.41, npm codewhale or crates.io codewhale-tui >=0.8.41 and <0.8.64, and crates.io deepseek-tui >=0.8.6 and <=0.8.41.