Unauthenticated RCE via WebSocket in @agentdeskai/browser-tools-server

Vulnerability Overview Vulnerability Name: Remote code execution via unauthenticated WebSocket in browser-tools-server CVE ID: No known CVE CVSS v3 base metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Confidentiality: High - Integrity: High - Availability: High Severity: 9.8 / 10 Impact Scope Affected Versions: - < 2.0.0 - < 2.0.0 Impact Description: - Complete remote code execution, running as the user executing the server. - Because the listener binds to 0.0.0.0 instead of localhost, attackers can access any host on the same LAN or shared Wi-Fi network. - Due to the same lack of authentication, any visited page can read captured console output and full HTTP request and response bodies (including Authorization and Cookie headers), trigger and retrieve screenshots of logged-in sessions, write arbitrary bytes to arbitrary file system paths, and overwrite server settings. Remediation Fixed Version: 2.0.0 Remediation Measures: - The connector binds to 127.0.0.1 and rejects non-loopback addresses. - The HTTP API requires a token generated for each session run, stored in the file. - WebSocket only accepts sources from , , and . Any HTTP(S) sources are constrained by the browser's settings, preventing pages from forging them. - The header is validated against DNS rebinding, and wildcard CORS has been removed. - AppleScript paths are completely removed. Captured values reaching the shell and screenshot names are restricted to and are internally resolved to a fixed directory. - The extension's network scanning feature has been removed, restricted to loopback only. - Settings allow using clamped ranges instead of merging from the request body. POC Code

Goal Reached Thanks to every supporter — we hit 100%!

Unauthenticated RCE via WebSocket in @agentdeskai/browser-tools-server

More from this source