@midscene/web is vulnerable to Missing Authentication for Critical Function
68
Medium Risk
Midscene bridge mode starts a local Socket.IO server that brokers browser automation commands between the CLI and the Chrome extension. The server is created with no CORS configuration, no Origin header validation, and no authentication token, so any web page loaded in the user's browser can open a cross-origin WebSocket connection to it. A connecting page can seize the single client slot to intercept and inject automation commands and read command-payload data, or immediately shut the server down by including the MIDSCENE_BRIDGE_SIGNAL_KILL query parameter. The fix restricts connections to trusted origins by validating the Origin header on every Socket.IO handshake.
You are affected if you are using a version that falls within the vulnerable range and you run Midscene in bridge mode, which starts the local Socket.IO bridge server. Exploitation additionally requires the user to visit an untrusted/externally-controlled web page while a bridge session is active.
@midscene/web is vulnerable to Missing Authentication for Critical Function in versions 0.8.17 - 1.10.3.
Upgrade the @midscene/web library to the patch version.
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant