First published: Thu May 08 2025(Updated: )
### Original Report 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 SETTINGS_MAX_HEADER_LIST_SIZE. 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. ### Impact Remote peers can cause the JVM to crash or continuously report OOM. ### Patches 12.0.17 ### Workarounds No workarounds. ### References https://github.com/jetty/jetty.project/issues/12690
Credit: emo@eclipse.org
Affected Software | Affected Version | How to fix |
---|---|---|
Mortbay Jetty | >=12.0.0<=12.0.16 | |
maven/org.eclipse.jetty.http2:jetty-http2-common | >=12.0.0<=12.0.16 | 12.0.17 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2025-1948 has a high severity rating due to the potential for denial of service caused by unvalidated HTTP/2 header sizes.
To fix CVE-2025-1948, update Eclipse Jetty to version 12.0.17 or later where the vulnerability is patched.
Eclipse Jetty versions from 12.0.0 to 12.0.16 are affected by CVE-2025-1948.
CVE-2025-1948 allows an attacker to cause denial of service by exploiting the error in handling large header list sizes.
As of now, there are no publicly disclosed active exploits for CVE-2025-1948, but the vulnerability poses a significant risk if left unpatched.