First published: Tue May 07 2024(Updated: )
An attacker can make the Node.js HTTP/2 server completely unavailable by sending a small amount of HTTP/2 frames packets with a few HTTP/2 frames inside. It is possible to leave some data in nghttp2 memory after reset when headers with HTTP/2 CONTINUATION frame are sent to the server and then a TCP connection is abruptly closed by the client triggering the Http2Session destructor while header frames are still being processed (and stored in memory) causing a race condition.
Affected Software | Affected Version | How to fix |
---|---|---|
F5 BIG-IP and BIG-IQ Centralized Management | =17.5.0>=17.1.0<=17.1.2 | 17.1.2.2 |
F5 BIG-IP and BIG-IQ Centralized Management | >=16.1.0<=16.1.6 | |
F5 BIG-IP and BIG-IQ Centralized Management | >=15.1.0<=15.1.10 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of F5-K000139532 is high due to its potential to render the Node.js HTTP/2 server completely unavailable.
F5-K000139532 affects F5 BIG-IP versions from 15.1.0 to 15.1.10, 16.1.0 to 16.1.4, and 17.1.0 to 17.1.1.
To fix F5-K000139532, you should upgrade your F5 BIG-IP to a version that is not affected by this vulnerability.
The impact of F5-K000139532 on your system is that it can lead to denial of service, making the HTTP/2 server unavailable.
Currently, there are no documented workarounds for F5-K000139532 other than applying the available updates.