Mousehole: Unauthenticated HTTP/WebSocket boundary exposes and mutates MAM cookie state
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| t-mart | mousehole | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| T-mart | Mousehole |
|
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.258% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
T-mart
T-mart mousehole |
|
| Vendors & Products |
T-mart
T-mart mousehole |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Mousehole is a background service to update a seedbox IP for MAM and web app to manage it. Prior to version 0.4.05, Mousehole's HTTP/WebSocket management boundary is reachable without application-layer authentication or browser/LAN provenance checks. The service stores a MyAnonamouse (MAM) session cookie in state and reuses the same cookie-bearing serialization for persisted state, public API responses, and WebSocket state updates. Any client that can reach the published Mousehole port can read cookie-bearing state, connect to WebSocket state updates, replace the stored cookie, or force MAM update side effects. The deployment examples publish port 5010 broadly with Docker's `5010:5010` syntax, which can make the issue reachable on mixed-trust LAN/VPN interfaces. Version 0.4.0 patches the issue. | |
| Title | Mousehole: Unauthenticated HTTP/WebSocket boundary exposes and mutates MAM cookie state | |
| Weaknesses | CWE-200 CWE-306 CWE-346 CWE-352 CWE-862 |
|
| References |
| |
| Metrics |
cvssV4_0
|