CodeWhale before 0.8.64 Remote Code Execution via allow_shell
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 0.8.41, 0.8.64
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: poc
- Automatable: no
- Technical impact: total
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: poc · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Hmbown CodeWhale
From 0.8.6 · fixed in 0.8.41
- Hmbown CodeWhale
From 0.8.6 · fixed in 0.8.41
- Hmbown CodeWhale
From 0.8.41 · fixed in 0.8.64
- Hmbown CodeWhale
From 0.8.41 · fixed in 0.8.64
- deepseek-tuicrates.io
From 0.8.6 · through 0.8.41
- deepseek-tuinpm
From 0.8.6 · fixed in 0.8.41
- codewhale-tuicrates.io
From 0.8.41 · fixed in 0.8.64
- codewhalenpm
From 0.8.41 · fixed in 0.8.64