The brace-expansion library generates arbitrary strings containing a common prefix and suffix. Prior to 1.1.20, 2.1.6, 3.0.8, and 5.0.11, deeply nested brace groups cause expand_() to recurse once per nesting level at comma-member and single-set expansion sites, exhausting the native stack before output limits can apply and potentially terminating the Node.js process. expand_ performs uncontrolled recursion for nested brace alternatives and single-part sets. deeply nested brace groups supplied as an untrusted pattern. expand_ is affected. expand is affected. Comma members is affected. Single set is affected. native stack exhaustion during nested sub-expansion. process-terminating denial of service. This issue is fixed in versions 1.1.20, 2.1.6, 3.0.8, and 5.0.11.
The product does not properly control the allocation and maintenance of a limited resource.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Red Hat Hardened Images | RedHat | nodejs26-main-11.19.1-1.26.10.0.0.2.hum1 | * |
| Red Hat Hardened Images | RedHat | nodejs22-main-10.9.9-1.22.23.3.2.3.2.1.hum1 | * |
| Red Hat Hardened Images | RedHat | nodejs24-main-11.19.0-1.24.21.0.1.1.hum1 | * |
| Red Hat Hardened Images | RedHat | nodejs22-main-10.9.9-1.22.23.3.2.3.2.2.hum1 | * |
| Red Hat Hardened Images | RedHat | nodejs24-main-11.19.0-1.24.21.0.1.2.hum1 | * |
| Red Hat Hardened Images | RedHat | nodejs26-main-11.19.1-1.26.10.0.0.3.hum1 | * |
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.