Horizon Alert
Summary of the vulnerability and why it matters
This Cross-Site WebSocket Hijacking vulnerability in nanobot allows any website to take control of your AI assistant. Because the security fix was incomplete, an attacker can hijack your session, read messages, steal QR codes, and send messages as you.
- Hijacked sessions can steal sensitive data.
- Users are at risk of impersonation.
- An attacker can gain full access to the bridge API.
Attack Path
How an attacker could exploit the issue
An attacker can exploit this by tricking a user into visiting a malicious website. This website will then communicate with the vulnerable Nanobot bridge service running on the user's local machine. By leveraging the Cross-Site WebSocket Hijacking flaw, the attacker can hijack the user's WhatsApp session, read messages, and steal QR codes.
- Requires user interaction.
- Targets local bridge service.
- User must run Nanobot bridge.
Live Threat
Current exploitation, exposure, and threat context
Attackers are unlikely to weaponize this CVE due to its restricted local access. While the impact of session hijacking is significant, the requirement for a user to visit a malicious website while the vulnerable software is running locally limits its broad exploitability.
- Local-only vulnerability.
- No public exploit available.
- Primarily impacts local user context.
Priority actions
Operational Fix
Recommended remediation, mitigation, and detection steps
Focus on identifying and isolating nanobot instances using versions prior to 0.1.5, as they are critically vulnerable to Cross-Site WebSocket Hijacking. This allows attackers to hijack sessions, steal QR codes, and send messages.
- Upgrade nanobot to version 0.1.5.
- Monitor for suspicious WebSocket connections to localhost:3001.
- Block access to the WebSocket API if possible.
