VDB
Sign up
HIGH7.5

GHSA-889j-63jv-qhr8

Eclipse Jetty HTTP/2 client can force the server to allocate a humongous byte buffer that may lead to OoM and subsequently the JVM to exit

Quick fix

GHSA-889j-63jv-qhr8 — org.eclipse.jetty.http2:jetty-http2-common: upgrade to the fixed version with the command below.

# pom.xml: bump <version>12.0.17</version> for org.eclipse.jetty.http2:jetty-http2-common

Details

### 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

Are you affected?

Enter the version of the package you're using.

Affected packages

Maven/org.eclipse.jetty.http2:jetty-http2-common
Introduced in: 12.0.0Fixed in: 12.0.17
Fix# pom.xml: bump <version>12.0.17</version> for org.eclipse.jetty.http2:jetty-http2-common

References