Java Websocket
Monthly
Unconstrained memory allocation in TooTallNate Java-WebSocket 1.6.0-1.6.1 allows remote unauthenticated attackers to exhaust server heap memory by sending WebSocket frames with arbitrarily large declared payload lengths. The Draft_6455 fragmentation handler initialized maxFrameSize to Integer.MAX_VALUE (~2 GiB), so the library attempts to allocate the full declared frame size before any payload data is actually received. A publicly available proof-of-concept exists via GitHub issue #1508; the upstream fix is in PR #1509 but has not yet shipped in a tagged release.
In Java-WebSocket less than or equal to 1.4.1, there is an Improper Validation of Certificate with Host Mismatch where WebSocketClient does not perform SSL hostname validation. Rated high severity (CVSS 8.1), this vulnerability is remotely exploitable, no authentication required. No vendor patch available.
Unconstrained memory allocation in TooTallNate Java-WebSocket 1.6.0-1.6.1 allows remote unauthenticated attackers to exhaust server heap memory by sending WebSocket frames with arbitrarily large declared payload lengths. The Draft_6455 fragmentation handler initialized maxFrameSize to Integer.MAX_VALUE (~2 GiB), so the library attempts to allocate the full declared frame size before any payload data is actually received. A publicly available proof-of-concept exists via GitHub issue #1508; the upstream fix is in PR #1509 but has not yet shipped in a tagged release.
In Java-WebSocket less than or equal to 1.4.1, there is an Improper Validation of Certificate with Host Mismatch where WebSocketClient does not perform SSL hostname validation. Rated high severity (CVSS 8.1), this vulnerability is remotely exploitable, no authentication required. No vendor patch available.