In Eclipse Jetty versions 12.0.0 to 12.0.16 included, an HTTP/2 client can specify a very large value for the HTTP/2 settings parameter SETTINGSMAXHEADERLISTSIZE. The Jetty HTTP/2 server does not perform validation on this setting, and tries to allocate a ByteBuffer of the specified capacity to encode HTTP responses, likely resulting in OutOfMemoryError being thrown, or even the JVM process exiting.
Remote peers can cause the JVM to crash or continuously report OOM.
12.0.17
No workarounds.
https://github.com/jetty/jetty.project/issues/12690
{ "nvd_published_at": "2025-05-08T18:15:41Z", "cwe_ids": [ "CWE-400" ], "severity": "HIGH", "github_reviewed": true, "github_reviewed_at": "2025-05-08T19:28:45Z" }