Loading vulnerability…
The HTTP server in Node.js 0.10.x before 0.10.21 and 0.8.x before 0.8.26 permits remote denial of service through uncontrolled memory and CPU consumption. An attacker can send a large number of HTTP pipelined requests while not reading server responses, causing server resource consumption.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains a single Metasploit auxiliary module: 'Node.js HTTP Pipelining Denial of Service'. The module targets a vulnerability (CVE-2013-4450) in Node.js HTTP servers prior to versions 0.10.21 and 0.8.26. The exploit works by sending a large number of pipelined HTTP requests over a single TCP connection to the target server, which causes unbounded memory allocation if the client does not read the responses. This can result in a denial of service (DoS) by exhausting the server's memory and potentially crashing the service. The module allows configuration of the target host (RHOST), port (RPORT, default 80), and the number of requests to send (RLIMIT, default 100000). The code is written in Ruby and is designed to be run within the Metasploit framework. No hardcoded IPs or URLs are present; the target is specified at runtime. The module includes a check method to help determine if the target is likely vulnerable. The overall structure is typical for a Metasploit DoS auxiliary module, with clear separation of initialization, checking, and attack logic.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.