نسخههای متأثر
- نسخههای متأثر
- نامشخص
- نسخهٔ اصلاحشده
- اعلام نشده
- نسخههای متأثر
- نامشخص
- نسخهٔ اصلاحشده
- اعلام نشده
بهرهبرداری
شرح آسیبپذیری
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.
A flaw was found in Jetty. A remote attacker can exploit this vulnerability by sending a specially crafted WebSocket frame with an unknown operation code (opcode) and a very large declared payload length. When auto-fragmentation is enabled, these unknown opcodes bypass the normal maximum frame size handling, leading Jetty to attempt a large memory allocation before validating the opcode. This can cause the Java Virtual Machine (JVM) heap to be exhausted, resulting in a Denial of Service (DoS) for the affected system.

