{"uuid": "f5794479-7f81-46fe-80cb-25fdf15fcc39", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-32640", "type": "seen", "source": "https://t.me/hacking_Attack/41068", "content": "verbose tracing of communications\n-d, \u2013debug Print each test case to track progress while running\n-u URL, \u2013url URL URL to connect to\n-f FILE, \u2013file FILE File containing URLs to check for valid WebSocket connections\n-n, \u2013no-encryption Connect using ws://, not wss:// (default is wss://)\n-k, \u2013nocert Ignore invalid SSL cert\n-o ORIGIN, \u2013origin ORIGIN\nSet origin\n-1 Test for generic Cross-site WebSocket Hijacking (CSWSH)\n-2 Test CVE-2021-32640 \u2013 ws Sec-Websocket-Protocol Regex DoS\n-3 Test CVE-2020-7662 & 7663 \u2013 faye Sec-WebSocket-Extensions Regex DoS\n-4 Test CVE-2020-27813 \u2013 Gorilla DoS Integer Overflow\n\nTest 1 provides a generic CSWSH test. This can be used in combination with the -oflag to specify a specific origin to attempt to bypass any server-side checks.\n\nTests 2, 3, and 4 check for specific CVEs. The test cases for these were created based on the PoC code published as part of the discovery of these CVEs. For example, to run test 4 on a local server on port 8084, you can run: python3 STEWS-vuln-detect.py -4 -n -u 127.0.0.1:8084Why this tool?\n\nWebSocket servers have been largely ignored in security circles. This is partially due to three hurdles that have not been clearly addressed for WebSocket endpoints:\n\n* Discovery\n* Enumeration/fingerprinting\n* Vulnerability detecting\n\nSTEWS attempts to address these three points. A custom tool was required because there is a distinct lack of support for manually configured WebSocket testing in current security testing tools:\n\n* There is a general lack of supported and scriptable Web Socket security testing tools (for example, NCC\u2019s unsupported\u00a0wssip tool,\u00a0nuclei\u2019s lack of Web Socket support, and\u00a0nmap\u2019s lack of Web Socket support)\n* Burp Suite lacks support for Web Socket extensions (for example, see\u00a0this Port Swigger forum thread\u00a0and\u00a0this one).\n* There is a lack of deeper Web Socket-specific security research (the\u00a0Awesome Web Socket Security repository\u00a0lists published Web Sockets security research)\n* The proliferation of Web Sockets around the modern web (as seen in the results of the STEWS discovery tool) Download", "creation_timestamp": "2026-09-01T20:01:57.460205Z"}