Description
A client may send a WebSocket frame with an unknown opcode and a very large declared payload length, causing Jetty to attempt a large memory allocation and potentially exhaust the JVM heap. This occurs when auto-fragmentation is enabled, as unknown opcodes bypass the normal maximum frame size handling and payload allocation occurs before the opcode is validated.
CVSS breakdown
CVSS 4.0
Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
None
Confidentiality (Vulnerable System)
None
Integrity (Vulnerable System)
None
Availability (Vulnerable System)
High
Confidentiality (Subsequent System)
None
Integrity (Subsequent System)
None
Availability (Subsequent System)
None
Affected products
- Eclipse Foundation / Eclipse Jetty12.1.0 – 12.1.11
- Eclipse Foundation / Eclipse Jetty12.0.0 – 12.0.37
- Eclipse Foundation / Eclipse Jetty11.0.0 – 11.0.31
- Eclipse Foundation / Eclipse Jetty10.0.0 – 10.0.31
References
Updated 44m ago · 8 sources