CyberRota Analysis
AI-GeneratedHTTPX2 versions 2.6.0 to 2.9.1 are vulnerable due to a failure to initiate TLS when using WebSocket connections over a SOCKS5 proxy, allowing sensitive data such as headers and cookies to be transmitted in plaintext. This vulnerability can be exploited by an attacker in control of the proxy path, enabling them to intercept or alter traffic and impersonate the WebSocket server. Organizations using affected versions of HTTPX2 should prioritize upgrading to version 2.10.0 or later to mitigate this high-severity risk.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
HTTPX2 is a next generation HTTP client for Python. Prior to 2.10.0, httpcore2 fails to start TLS in src/httpcore2/httpcore2/_sync/socks_proxy.py and src/httpcore2/httpcore2/_async/socks_proxy.py when the remote origin uses wss through a SOCKS5 proxy because the TLS upgrade condition only recognizes https. HTTPX2 exposes the flaw through Client.websocket() and AsyncClient.websocket() from 2.6.0 through 2.9.1, so the opening handshake, query parameters, Authorization headers, cookies, and subsequent frames can cross the proxy path in plaintext without certificate verification. An attacker controlling or observing that path can read or modify traffic and impersonate the WebSocket server. This issue is fixed in httpcore2 2.10.0 and HTTPX2 2.10.0.