Security Resilience

CVE-2024-21536

DoS in Chimurai Http-Proxy-Middleware ≤ 2.0.7

Public PoCDoS
Published
19 October 2024
Modified
01 August 2026
Patch / advisory
CVSS Score v4 7.7
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.010 63th percentile
Risk Priority 45 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2024-21536 is a high-severity Uncontrolled Resource Consumption (CWE-400) vulnerability in Chimurai Http-Proxy-Middleware. Its CVSS base score is 7.7 (High).

Operationally, ranked in the top 37% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SC-5 (Denial-of-service Protection) and SC-6 (Resource Availability) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

Versions of the package http-proxy-middleware before 2.0.7, from 3.0.0 and before 3.0.3 are vulnerable to Denial of Service (DoS) due to an UnhandledPromiseRejection error thrown by micromatch. An attacker could kill the Node.js process and crash the server by making…

more

requests to certain paths.

CWE(s)

Related Threats

CVEs Like This One

CVE-2026-55603Same product: Chimurai Http-Proxy-Middleware
CVE-2025-32997Same product: Chimurai Http-Proxy-Middleware
CVE-2026-55602Same product: Chimurai Http-Proxy-Middleware
CVE-2025-32996Same product: Chimurai Http-Proxy-Middleware
CVE-2026-47077Shared CWE-400
CVE-2023-52425Shared CWE-400
CVE-2026-110871Shared CWE-400
CVE-2025-13836Shared CWE-400
CVE-2026-22740Shared CWE-400
CVE-2023-31418Shared CWE-400

Affected Assets

chimurai
http-proxy-middleware
≤ 2.0.7 · 3.0.0 — 3.0.3

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

SC-5 directly limits the effects of resource-exhaustion events that constitute uncontrolled consumption.

SC-6 enforces explicit allocation limits on resources, structurally preventing the weakness from occurring.

Process isolation confines resource consumption to separate domains, reducing blast radius without stopping the root flaw.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Pre-agreed severity-based prioritization and resource allocation during incident triage reduce the likelihood that an attacker-induced resource exhaustion will overwhelm the organization before corrective action is taken.

finds

Early notification of anomalous resource consumption or system malfunctions enables throttling or isolation before availability is lost.

A.8.15 Logging partial match
finds

Specifying log storage limits and rotation procedures reduces the risk that unbounded log growth will exhaust disk or memory resources and cause denial of service.

finds

Resource-utilization monitoring and alerting on bottlenecks or overloads limits the impact of denial-of-service or resource-exhaustion attacks.

blocks

A.8.20 implements network-level protections (firewalls, segmentation, protocol hardening, monitoring, authentication of systems/devices) that can limit abuse of a resource-consuming weakness but do not stop the weakness from being exploitable; the flaw remains present in the product and can still be triggered from an authorized or internal context.

blocks

Monitoring network service usage and applying controls to restrict access when necessary limits an attacker’s ability to consume excessive resources through unrestricted or unauthenticated service calls.

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

  • No fine-grained STIG row for CWE-400, a class-level weakness. Rules are authored against its narrower children: CWE-770.

References