CodeWhale Package Vulnerability: SSRF Bypass Due to DNS Pinning Failure
- Severity
- HIGH
- Affected component
- deepseek-tui (cargo)
- Affected versions
- < 0.8.26 or < 0.8.26 or < 0.8.22 or >= 0.8.32, <= 0.8.41 or >= 0.3.0, < 0.8.23
- Patched version
- 0.8.64
An early warning has been issued for a vulnerability in the CodeWhale package that allows a bypass of SSRF mitigations due to a DNS pinning failure. Versions before 0.8.64 are reportedly affected.
What happened
The CodeWhale package, specifically versions before 0.8.64, has been identified with a vulnerability that enables a bypass of Server-Side Request Forgery (SSRF) mitigations. This is due to a failure in DNS pinning, which is a security measure intended to prevent DNS spoofing attacks. The vulnerability is tracked under GHSA-6v2g-fpxh-pmmh and has been flagged as high severity. It is under investigation and has not yet been exploited in the wild.
Affected components include deepseek-tui (cargo) for versions less than 0.8.26 or between 0.8.32 and 0.8.41, and codewhale (npm) for versions between 0.8.41 and 0.8.64. The recommended action is to upgrade to version 0.8.64 or later for both deepseek-tui and codewhale packages to mitigate the risk.
What to do about it
- Identify and list all instances where the CodeWhale package is used within your projects.
- Check the version of the CodeWhale package in use and compare it against the affected version ranges.
- Upgrade to version 0.8.64 or later for both deepseek-tui and codewhale packages as a mitigation step.
- Monitor the primary sources for updates on the vulnerability and any additional mitigation advice.
- Consider implementing additional security measures to protect against SSRF attacks while the upgrade is being performed.
How 0Day would have caught this
deepseek-tui is anywhere in your dependency tree, the engineers who own the affected repositories get a push alert the moment it is flagged — no manual audit to remember to run.Read how this differs from waiting on a scanner to catch a known advisory, or see the exact, read-only access 0Day needs to do this for an organization.
Frequently asked questions
Am I affected?
You are potentially affected if you are using deepseek-tui (cargo) versions less than 0.8.26 or between 0.8.32 and 0.8.41, or codewhale (npm) versions between 0.8.41 and 0.8.64.
What should I do right now?
Immediately check your project dependencies for the affected versions of deepseek-tui and codewhale. Upgrade to version 0.8.64 or later for both packages.
Is there an official fix available?
Yes, version 0.8.64 or later is the recommended fix for both deepseek-tui and codewhale packages.
Sources
- [GHSA-62f5-cp2p-vq95] CodeWhale: Project config `instructions` override enables arbitrary file read into AI system prompt via cloned repository
- [GHSA-6v2g-fpxh-pmmh] CodeWhale: SSRF bypass - TOCTOU on DNS failure for DNS pinning
- [GHSA-7j5w-7r7x-9v27] CodeWhale: Argument Injection in `git_show` Tool Allows Arbitrary File Write Without Approval
- [GHSA-c6mw-8xh8-gpq6] CodeWhale: Argument Injection in `git_blame` Tool Allows Arbitrary File Read Without Approval
- [GHSA-g29h-pfmp-qp9r] CodeWhale: exec_shell_interact sends LLM-controlled input to a running shell without an approval prompt (privilege escalation)
- [GHSA-gx45-xrj5-g6c4] CodeWhale: Project config `allow_shell` override enables arbitrary shell command execution via cloned repository
- [GHSA-h539-c7r8-3xq4] CodeWhale: js_execution leaks parent environment to model context via missing env scrub
- [GHSA-6v2g-fpxh-pmmh] CodeWhale: SSRF bypass - TOCTOU on DNS failure for DNS pinning