JunoClaw: MCP write tools exposed raw BIP-39 mnemonic as a tool-call parameter
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Dragonmonk111 | junoclaw | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Dragonmonk111 | Junoclaw |
|
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.225% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Dragonmonk111
Dragonmonk111 junoclaw |
|
| Vendors & Products |
Dragonmonk111
Dragonmonk111 junoclaw |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | JunoClaw is an agentic AI platform built on Juno Network. Prior to 0.x.y-security-1, every MCP write tool (send_tokens, execute_contract, instantiate_contract, upload_wasm, ibc_transfer, etc.) accepted 'mnemonic: string' as an explicit tool-call parameter. The BIP-39 seed was consequently embedded in the LLM tool-call JSON, exposing it to any transport, log, or telemetry surface in the path between the LLM provider and the MCP process. This vulnerability is fixed in 0.x.y-security-1. | |
| Title | JunoClaw: MCP write tools exposed raw BIP-39 mnemonic as a tool-call parameter | |
| Weaknesses | CWE-200 CWE-312 CWE-522 CWE-532 |
|
| References |
| |
| Metrics |
cvssV3_1
|