Eclipse Foundation Eclipse Jetty
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.
First public PoC
None yetno public PoC found
Public PoCs00 on GitHub
CVSS8.7high · scored by CNA · CWE-770
CISA KEV
Not listednot known exploited
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
Eclipse Foundation Eclipse Jetty
- >= 12.1.0, <= 12.1.11
- >= 12.0.0, <= 12.0.37
- >= 11.0.0, <= 11.0.31
- >= 10.0.0, <= 10.0.31
Mitigation
The record names no fix. Check the vendor advisory below.
References
- Vendor advisory github.com/jetty/jetty.project/security/adviso…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.