Skip to content
Fencer Vulns
medium 5.3

CVE-2024-28182 json

Reading unbounded number of HTTP/2 CONTINUATION frames to cause excessive CPU usage

published 2024-04-04 2 y ago modified 2026-10-15 25 d ago also EUVD-2024-25307 , JLSEC-2026-4

cvss
5.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
82.0%
EPSS 82.0% chance of exploitation in 30 days, percentile 99.6%
public exploits
0
none known

Summary

nghttp2 is an implementation of the Hypertext Transfer Protocol version 2 in C. The nghttp2 library prior to version 1.61.0 keeps reading the unbounded number of HTTP/2 CONTINUATION frames even after a stream is reset to keep HPACK context in sync. This causes excessive CPU usage to decode HPACK stream. nghttp2 v1.61.0 mitigates this vulnerability by limiting the number of CONTINUATION frames it accepts per stream. There is no workaround for this vulnerability.

Patch / fix

  • julia nghttp2_jll 1.61.0+0
  • nghttp2 nghttp2 1.61.0
  • Siemens SIMATIC S7-1500 CPU 1518-4 PN/DP MFP V3.1.5
  • Siemens SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP V3.1.5
  • Siemens SINEC NMS V3.0
  • Siemens SIPLUS S7-1500 CPU 1518-4 PN/DP MFP V3.1.5
  • nghttp2 Debian 12 1.52.0-1+deb12u2
  • nghttp2 Debian 14, Debian 13 1.61.0-1

debian advisories DEBIAN-CVE-2024-28182

  • nghttp2 Ubuntu 20.04 LTS 1.40.0-1ubuntu0.3
  • nghttp2 Ubuntu 22.04 LTS 1.43.0-1ubuntu0.2
  • nghttp2 Ubuntu 24.04 LTS 1.59.0-1ubuntu0.1
  • nghttp2 Ubuntu Pro 16.04 LTS 1.7.1-1ubuntu0.1~esm2
  • nghttp2 Ubuntu Pro 18.04 LTS 1.30.0-1ubuntu1+esm2

ubuntu advisories UBUNTU-CVE-2024-28182

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • jbcs-httpd24-curl jboss core services 1 8.7.1-2.el7jbcs
  • jbcs-httpd24-curl jboss core services 1 8.7.1-2.el8jbcs
  • jbcs-httpd24-httpd jboss core services 1 2.4.57-10.el7jbcs
  • jbcs-httpd24-httpd jboss core services 1 2.4.57-10.el8jbcs
  • jbcs-httpd24-mod_jk jboss core services 1 1.2.49-6.redhat_1.el7jbcs
  • jbcs-httpd24-mod_jk jboss core services 1 1.2.49-6.redhat_1.el8jbcs
  • jbcs-httpd24-mod_md jboss core services 1 1:2.4.24-6.el7jbcs
  • jbcs-httpd24-mod_md jboss core services 1 1:2.4.24-6.el8jbcs

red hat advisories RHSA-2024:2693RHSA-2024:4721RHSA-2024:2910RHSA-2024:2853RHSA-2024:2780RHSA-2024:2778

  • nghttp2 Linux Micro 6.0 1.52.0-5.1
  • nghttp2 SLE Module for Basesystem 15 SP5, SLE Micro 5.5, SLE Micro 5.4 +19 more 1.40.0-150200.17.1
  • nghttp2-python openSUSE Leap 15.5 1.40.0-150200.17.1
  • nghttp2 SLES for SAP 12 SP5, SLES 12 SP5, SLE Software Development Kit 12 SP5 1.39.2-3.18.1

suse advisories SUSE-SU-2025:20002-1SUSE-SU-2024:1167-2SUSE-SU-2024:1167-1SUSE-SU-2024:1156-1

  • nghttp2 openSUSE Tumbleweed 1.61.0-1.1

opensuse advisories openSUSE-SU-2024:13825-1

  • nghttp2 AlmaLinux 8 1.33.0-6.el8_10.1
  • libnghttp2 AlmaLinux 8 1.33.0-6.el8_10.1
  • nghttp2 AlmaLinux 9 1.43.0-5.el9_4.3
  • libnghttp2 AlmaLinux 9 1.43.0-5.el9_4.3
  • nodejs AlmaLinux 9 1:16.20.2-8.el9_4
  • npm AlmaLinux 9 1:8.19.4-1.16.20.2.8.el9_4
  • nodejs-libs AlmaLinux 9 1:16.20.2-8.el9_4
  • nodejs-full-i18n AlmaLinux 9 1:16.20.2-8.el9_4

almalinux advisories ALSA-2024:4252ALSA-2024:3501ALSA-2024:2910ALSA-2024:2853ALSA-2024:2778ALSA-2024:2779

  • nghttp2 Rocky Linux 8 1.33.0-6.el8_10.1
  • nodejs-nodemon Rocky Linux 9 3.0.1-1.module+el9.5.0+31770+0da7192d
  • nodejs-nodemon Rocky Linux 9 3.0.1-1.module+el9.6.0+32322+a8b1fd01
  • nodejs-nodemon Rocky Linux 9 3.0.1-1.module+el9.6.0+32045+2e5d342d
  • nodejs-nodemon Rocky Linux 9 3.0.1-1.module+el9.6.0+32143+ae966e5b
  • nodejs-nodemon Rocky Linux 9 3.0.1-1.module+el9.6.0+32144+1d29a396
  • nodejs-nodemon Rocky Linux 9 3.0.1-1.module+el9.6.0+32185+bd121a25
  • nodejs-packaging Rocky Linux 9 2021.06-4.module+el9.5.0+31770+0da7192d

rocky linux advisories RLSA-2024:4252RLSA-2024:2853RLSA-2024:2910RLSA-2024:3501RLSA-2024:2779RLSA-2024:2778

  • rust Azure Linux 3.0 1.75.0-1
  • cmake Azure Linux 3.0 3.29.6-1
  • nodejs Azure Linux 3.0 20.14.0-1
  • nghttp2 Azure Linux 3.0 1.61.0-1
  • cmake CBL-Mariner 2.0 3.21.4-14
  • nodejs18 CBL-Mariner 2.0 18.20.3-1
  • nghttp2 CBL-Mariner 2.0 1.57.0-2
  • rust CBL-Mariner 2.0 1.68.0-1

azure linux advisories AZL-38719AZL-38728AZL-38881AZL-38995AZL-39115AZL-39148

Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2024-28182 updated cvss 5.3

nghttp2: CONTINUATION frames DoS

  • Red Hat Enterprise Linux 8 npm, nodejs, nodejs-libs, nodejs-nodemon, nodejs-full-i18n, nodejs-packaging, +1 more Red Hat Software Collections httpd24-nghttp2, rh-nodejs14-npm, httpd24-libnghttp2, rh-nodejs14-nodejs, rh-nodejs14-nodejs-full-i18n
    affected: workaround, no fix planned “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.”
  • Red Hat CodeReady Linux Builder EUS (v.8.8) nghttp2 1.33.0-5.el8_8.1
    fixed: vendor fix “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.” RHSA-2024:3701
  • Red Hat CodeReady Linux Builder EUS (v.9.2) nghttp2 1.43.0-5.el9_2.3
    fixed: vendor fix “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.” RHSA-2024:3665
  • Red Hat Enterprise Linux AppStream (v. 8) nodejs 18.20.2-1.module+el8.9.0+21767+537f34ee, nodejs 20.12.2-2.module+el8.9.0+21743+0b3f1be2, nodejs-nodemon 3.0.1-1.module+el8.9.0+20473+c4e3d824, nodejs-nodemon 3.0.1-1.module+el8.9.0+21190+5ebd2c33, npm 10.5.0-1.18.20.2.1.module+el8.9.0+21767+537f34ee, npm 10.5.0-1.20.12.2.2.module+el8.9.0+21743+0b3f1be2, +6 more
    fixed: vendor fix “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.” RHSA-2024:2780
  • Red Hat Enterprise Linux AppStream (v. 9) nodejs 16.20.2-8.el9_4, nodejs-libs 16.20.2-8.el9_4, npm 8.19.4-1.16.20.2.8.el9_4, nodejs-full-i18n 16.20.2-8.el9_4, nodejs 18.20.2-2.module+el9.4.0+21742+692df1ea, nodejs 20.12.2-2.module+el9.4.0+21731+46b5b8a7, +10 more
    fixed: vendor fix “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.” RHSA-2024:2910
  • Red Hat Enterprise Linux AppStream E4S (v.9.0) nodejs 16.20.2-9.el9_0, nodejs-libs 16.20.2-9.el9_0, npm 8.19.4-1.16.20.2.9.el9_0, nodejs-full-i18n 16.20.2-9.el9_0
    fixed: vendor fix “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.” RHSA-2024:4721
  • Red Hat Enterprise Linux AppStream EUS (v.8.8) nodejs 18.19.1-3.module+el8.8.0+22005+6f8bb252, nodejs-nodemon 3.0.1-1.module+el8.8.0+19757+8ca87034, npm 10.2.4-1.18.19.1.3.module+el8.8.0+22005+6f8bb252, nodejs-full-i18n 18.19.1-3.module+el8.8.0+22005+6f8bb252, nodejs-packaging 2021.06-4.module+el8.7.0+15582+19c314fa, nodejs-packaging-bundler 2021.06-4.module+el8.7.0+15582+19c314fa
    fixed: vendor fix “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.” RHSA-2024:4824
  • Red Hat Enterprise Linux AppStream EUS (v.9.2) nodejs 16.20.2-5.el9_2.3, nodejs-libs 16.20.2-5.el9_2.3, npm 8.19.4-1.16.20.2.5.el9_2.3, nodejs-full-i18n 16.20.2-5.el9_2.3, nodejs 18.20.2-2.module+el9.2.0+21812+f1e61652, npm 10.5.0-1.18.20.2.2.module+el9.2.0+21812+f1e61652, +4 more
    fixed: vendor fix “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.” RHSA-2024:2937
show 17 more
  • Red Hat Enterprise Linux BaseOS (v. 8) nghttp2 1.33.0-6.el8_10.1, libnghttp2 1.33.0-6.el8_10.1
    fixed: vendor fix “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.” RHSA-2024:4252
  • Red Hat Enterprise Linux BaseOS (v. 9) nghttp2 1.43.0-5.el9_4.3, libnghttp2 1.43.0-5.el9_4.3
    fixed: vendor fix “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.” RHSA-2024:3501
  • Red Hat Enterprise Linux BaseOS AUS (v. 8.2) nghttp2 1.33.0-3.el8_2.3, libnghttp2 1.33.0-3.el8_2.3
    fixed: vendor fix “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.” RHSA-2024:4576
  • Red Hat Enterprise Linux BaseOS AUS (v.8.4) nghttp2 1.33.0-4.el8_4.2, libnghttp2 1.33.0-4.el8_4.2
    fixed: vendor fix “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.” RHSA-2024:4732
  • Red Hat Enterprise Linux BaseOS AUS (v.8.6) nghttp2 1.33.0-4.el8_6.2, libnghttp2 1.33.0-4.el8_6.2
    fixed: vendor fix “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.” RHSA-2024:3763
  • Red Hat Enterprise Linux BaseOS E4S (v.8.4) nghttp2 1.33.0-4.el8_4.2, libnghttp2 1.33.0-4.el8_4.2
    fixed: vendor fix “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.” RHSA-2024:4732
  • Red Hat Enterprise Linux BaseOS E4S (v.8.6) nghttp2 1.33.0-4.el8_6.2, libnghttp2 1.33.0-4.el8_6.2
    fixed: vendor fix “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.” RHSA-2024:3763
  • Red Hat Enterprise Linux BaseOS E4S (v.9.0) nghttp2 1.43.0-5.el9_0.3, libnghttp2 1.43.0-5.el9_0.3
    fixed: vendor fix “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.” RHSA-2024:3875
  • Red Hat Enterprise Linux BaseOS EUS (v.8.8) nghttp2 1.33.0-5.el8_8.1, libnghttp2 1.33.0-5.el8_8.1
    fixed: vendor fix “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.” RHSA-2024:3701
  • Red Hat Enterprise Linux BaseOS EUS (v.9.2) nghttp2 1.43.0-5.el9_2.3, libnghttp2 1.43.0-5.el9_2.3
    fixed: vendor fix “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.” RHSA-2024:3665
  • Red Hat Enterprise Linux BaseOS TUS (v.8.4) nghttp2 1.33.0-4.el8_4.2, libnghttp2 1.33.0-4.el8_4.2
    fixed: vendor fix “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.” RHSA-2024:4732
  • Red Hat Enterprise Linux BaseOS TUS (v.8.6) nghttp2 1.33.0-4.el8_6.2, libnghttp2 1.33.0-4.el8_6.2
    fixed: vendor fix “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.” RHSA-2024:3763
  • Red Hat Enterprise Linux CRB (v. 8) nghttp2 1.33.0-6.el8_10.1
    fixed: vendor fix “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.” RHSA-2024:4252
  • Red Hat Enterprise Linux CRB (v. 9) nghttp2 1.43.0-5.el9_4.3
    fixed: vendor fix “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.” RHSA-2024:3501
  • Red Hat JBoss Core Services
    fixed: vendor fix “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.” RHSA-2024:2694
  • Red Hat JBoss Core Services on RHEL 7 Server jbcs-httpd24-curl 8.7.1-2.el7jbcs, jbcs-httpd24-httpd 2.4.57-10.el7jbcs, jbcs-httpd24-libcurl 8.7.1-2.el7jbcs, jbcs-httpd24-mod_md 2.4.24-6.el7jbcs, jbcs-httpd24-mod_ssl 2.4.57-10.el7jbcs, jbcs-httpd24-nghttp2 1.43.0-13.el7jbcs, +11 more Red Hat JBoss Core Services on RHEL 8 jbcs-httpd24-curl 8.7.1-2.el8jbcs, jbcs-httpd24-httpd 2.4.57-10.el8jbcs, jbcs-httpd24-libcurl 8.7.1-2.el8jbcs, jbcs-httpd24-mod_md 2.4.24-6.el8jbcs, jbcs-httpd24-mod_ssl 2.4.57-10.el8jbcs, jbcs-httpd24-nghttp2 1.43.0-13.el8jbcs, +11 more
    fixed: vendor fix “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.” RHSA-2024:2693
  • Red Hat Enterprise Linux 10 nghttp2, nodejs20
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

cisa ICSA-23-348-10 updated cvss 5.3

Siemens SIMATIC S7-1500

  • Siemens SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AB0) >= 3.1.0, < 3.1.5 Siemens SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AC0) >= 3.1.0, < 3.1.5 Siemens SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AB0) >= 3.1.0, < 3.1.5 Siemens SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AC0) >= 3.1.0, < 3.1.5 Siemens SIPLUS S7-1500 CPU 1518-4 PN/DP MFP (6AG1518-4AX00-4AC0) >= 3.1.0, < 3.1.5
    affected: fixed in V3.1.5, mitigation support.industry.siemens.com

Facts from CISA's republication of the vendor's own advisory (CSAF); the linked advisory is the authoritative source. CISA notification · csaf

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
2 y ago

Exploit prediction

81.99% chance of exploitation in the next 30 days, higher than 99.6% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
OSV 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Affected packages

ecosystem package affected fixed in
julia nghttp2_jll
<1.61.0+0
1.61.0+0

Affected products

  • nghttp2 nghttp2
  • Siemens SIMATIC S7-1500 CPU 1518-4 PN/DP MFP
  • Siemens SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP
  • Siemens SINEC NMS
  • Siemens SIPLUS S7-1500 CPU 1518-4 PN/DP MFP

Classification

Weakness
  • CWE-770 Allocation of Resources Without Limits or Throttling

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.