This is a summary of the AI-generated 10-question deep analysis. The full version (longer answers, follow-up Q&A, related CVEs) requires login. Read the full analysis โ
Q1What is this vulnerability? (Essence + Consequences)
๐จ **Essence**: Apache Tomcat WebSocket module fails to validate payload lengths correctly. ๐ฅ **Consequences**: Triggers an **infinite loop** during frame processing, leading to a **Denial of Service (DoS)**.โฆ
๐ก๏ธ **Root Cause**: Lack of proper validation for **WebSocket frame payload length**. ๐ **CWE**: Not explicitly listed in data, but technically relates to **Input Validation** failures leading to resource exhaustion.
Q3Who is affected? (Versions/Components)
๐ฆ **Affected Products**: Apache Tomcat. ๐ **Affected Versions**: โข 10.0.0-M1 to 10.0.0-M6 โข 9.0.0.M1 to 9.0.36 โข 8.5.0 to 8.5.56 โข 7.0.27 to 7.0.104
Q4What can hackers do? (Privileges/Data)
๐ฎ **Attacker Action**: Send multiple malicious requests with invalid payload lengths. ๐ **Impact**: Causes **DoS** (Service Down). โ ๏ธ **Privileges**: No code execution or data theft mentioned; purely availability impact.
Q5Is exploitation threshold high? (Auth/Config)
๐ **Threshold**: **Low**. โ๏ธ **Config**: Requires access to the WebSocket endpoint. ๐ซ **Auth**: No authentication required to exploit the logic flaw itself, just network reachability to the WS port.
Q6Is there a public Exp? (PoC/Wild Exploitation)
๐ป **Public Exploit**: **YES**. ๐ **Resources**: GitHub repos like `RedTeamPentesting/CVE-2020-13935` provide `tcdos` binary. ๐ **Status**: Wild exploitation is possible via simple Go-based tools.
Q7How to self-check? (Features/Scanning)
๐ **Self-Check**: Use the `tcdos` tool against your WebSocket endpoints. ๐ก **Scanning**: Nuclei templates (`CVE-2020-13935.yaml`) available for automated detection.โฆ
๐ฅ **Urgency**: **HIGH**. โก **Priority**: Critical for availability. Since public exploits exist and it causes DoS, patch immediately or apply network-level mitigations. Don't wait!