| Package | Affected versions | Patched versions |
|---|---|---|
| nghttp2 | < 1.41.0 | 1.41.0 |
| node.js | ≥ 10.0.0, ≤ 10.12.0≥ 10.13.0, < 10.21.0≥ 12.0.0, ≤ 12.12.0≥ 12.13.0, < 12.18.0≥ 14.0.0, ≤ 14.4.0 | 10.21.012.18.0 |
| banking extensibility workbench | = 14.3.0= 14.4.0 | |
| blockchain platform | < 21.1.2 | 21.1.2 |
| enterprise communications broker | = 3.1.0= 3.2.0 | |
| graalvm | = 19.3.2= 20.1.0 | |
| mysql | ≥ 7.3.0, ≤ 7.3.30≥ 7.4.0, ≤ 7.4.29≥ 7.5.0, ≤ 7.5.19≥ 7.6.0, ≤ 7.6.15≥ 8.0.0, ≤ 8.0.21 |
In nghttp2 before version 1.41.0, the overly large HTTP/2 SETTINGS frame payload causes denial of service. The proof of concept attack involves a malicious client constructing a SETTINGS frame with a length of 14,400 bytes (2400 individual settings entries) over and over again. The attack causes the CPU to spike at 100%. nghttp2 v1.41.0 fixes this vulnerability. There is a workaround to this vulnerability. Implement nghttp2_on_frame_recv_callback callback, and if received frame is SETTINGS frame and the number of settings entries are large (e.g., > 32), then drop the connection.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free