p PatchFirst

CVE-2024-27983

CVE-2024-27983

This page contains facts from public vulnerability sources. Check the original advisory before updating.

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.

CVSS 8.2 · High · EPSS 87.2% · Fix available

Published
Updated

Stack: system · node

Affected products and versions

  • node.js

    Versions
    • ≥ 4.0, < 4.*: Affected (semver)
    • ≥ 5.0, < 5.*: Affected (semver)
    • ≥ 6.0, < 6.*: Affected (semver)
    • ≥ 7.0, < 7.*: Affected (semver)
    • ≥ 8.0, < 8.*: Affected (semver)
    • ≥ 9.0, < 9.*: Affected (semver)
    • ≥ 10.0, < 10.*: Affected (semver)
    • ≥ 11.0, < 11.*: Affected (semver)
    • ≥ 12.0, < 12.*: Affected (semver)
    • ≥ 13.0, < 13.*: Affected (semver)
    • ≥ 14.0, < 14.*: Affected (semver)
    • ≥ 15.0, < 15.*: Affected (semver)
    • ≥ 16.0, < 16.*: Affected (semver)
    • ≥ 17.0, < 17.*: Affected (semver)
    • ≥ 18.0, < 18.20.1: Affected (semver)
    • ≥ 19.0, < 19.*: Affected (semver)
    • ≥ 20.0, < 20.12.1: Affected (semver)
    • ≥ 21.0, < 21.7.2: Affected (semver)

    Update to 18.20.1; Update to 20.12.1; Update to 21.7.2

  • nodejs Debian:12

    Versions
    • 18.13.0+dfsg1-1
    • 18.13.0+dfsg1-1.1
    • 18.19.0+dfsg-1
    • 18.19.0+dfsg-2
    • 18.19.0+dfsg-3
    • 18.19.0+dfsg-4
    • 18.19.0+dfsg-5
    • 18.19.0+dfsg-6
    • 18.19.0+dfsg-6~deb12u1
    • 18.19.0+dfsg-6~deb12u2
    • 18.19.1+dfsg-1
    • 18.19.1+dfsg-2
    • 18.19.1+dfsg-3
    • 18.19.1+dfsg-3.1
    • 18.19.1+dfsg-4
    • 18.19.1+dfsg-6
    • 18.20.1+dfsg-1
    • 18.20.1+dfsg-2
    • 18.20.1+dfsg-3
    • 18.20.1+dfsg-4
    Affected ranges
    • ECOSYSTEM: < 18.20.4+dfsg-1~deb12u1

    Update to 18.20.4+dfsg-1~deb12u1

  • nodejs Debian:13

    Affected ranges
    • ECOSYSTEM: < 18.20.1+dfsg-1

    Update to 18.20.1+dfsg-1

  • nodejs Debian:14

    Affected ranges
    • ECOSYSTEM: < 18.20.1+dfsg-1

    Update to 18.20.1+dfsg-1

  • nodejs Ubuntu:Pro:20.04:LTS

    Versions
    • 10.15.2~dfsg-2ubuntu1
    • 10.17.0~dfsg-2ubuntu4
    • 10.17.0~dfsg-2ubuntu6
    • 10.19.0~dfsg-3ubuntu1
    • 10.19.0~dfsg-3ubuntu1.1
    • 10.19.0~dfsg-3ubuntu1.2
    • 10.19.0~dfsg-3ubuntu1.3
    • 10.19.0~dfsg-3ubuntu1.5
    • 10.19.0~dfsg-3ubuntu1.6
    • 10.19.0~dfsg-3ubuntu1.6+esm2
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • nodejs Ubuntu:Pro:22.04:LTS

    Versions
    • 12.22.5~dfsg-5ubuntu1
    • 12.22.7~dfsg-2ubuntu1
    • 12.22.7~dfsg-2ubuntu3
    • 12.22.9~dfsg-1ubuntu2
    • 12.22.9~dfsg-1ubuntu3
    • 12.22.9~dfsg-1ubuntu3.1
    • 12.22.9~dfsg-1ubuntu3.2
    • 12.22.9~dfsg-1ubuntu3.3
    • 12.22.9~dfsg-1ubuntu3.4
    • 12.22.9~dfsg-1ubuntu3.5
    • 12.22.9~dfsg-1ubuntu3.6
    • 12.22.9~dfsg-1ubuntu3.6+esm2
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • nodejs Ubuntu:24.04:LTS

    Versions
    • 18.13.0+dfsg1-1ubuntu2
    • 18.19.1+dfsg-2ubuntu4
    • 18.19.1+dfsg-6ubuntu1
    • 18.19.1+dfsg-6ubuntu2
    • 18.19.1+dfsg-6ubuntu5
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

Original sources

Check your server →