A flaw in Node.js HTTP/2 handling can cause HTTP/2 retained header blocks evade maxSessionMemory and enable remote memory exhaustion.
This vulnerability affects Node.js 24.x and 22.x.
Weakness
The product does not properly control the allocation and maintenance of a limited resource.
Affected Software
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Red Hat Enterprise Linux 10 | RedHat | nodejs22-1:22.23.2-1.el10_2 | * |
| Red Hat Enterprise Linux 10 | RedHat | nodejs24-1:24.19.0-1.el10_2 | * |
| Red Hat Enterprise Linux 10.0 Extended Update Support | RedHat | nodejs22-1:22.23.2-1.el10_0 | * |
| Red Hat Enterprise Linux 8 | RedHat | nodejs:22-8100020260819113925.6d880403 | * |
| Red Hat Enterprise Linux 8 | RedHat | nodejs:24-8100020260819113942.6d880403 | * |
| Red Hat Enterprise Linux 9 | RedHat | nodejs:22-9080020260819113937.rhel9 | * |
| Red Hat Enterprise Linux 9 | RedHat | nodejs:24-9080020260819113946.rhel9 | * |
| Red Hat Enterprise Linux 9.6 Extended Update Support | RedHat | nodejs:22-9060020260901085634.rhel9 | * |
| Red Hat Hardened Images | RedHat | nodejs22-main-22.23.2-2.3.hum1 | * |
| Red Hat Hardened Images | RedHat | nodejs24-main-24.18.1-0.1.hum1 | * |
Potential Mitigations
Mitigation of resource exhaustion attacks requires that the target system either:
The first of these solutions is an issue in itself though, since it may allow attackers to prevent the use of the system by a particular valid user. If the attacker impersonates the valid user, they may be able to prevent the user from accessing the server in question.
The second solution is simply difficult to effectively institute – and even when properly done, it does not provide a full solution. It simply makes the attack require more resources on the part of the attacker.
Related Attack Patterns
- https://cwe.mitre.org/data/definitions/147.html
- https://cwe.mitre.org/data/definitions/227.html
- https://cwe.mitre.org/data/definitions/492.html