A stack consumption vulnerability exists in the ASP implementation of Microsoft Internet Information Services (IIS) versions 5.1, 6.0, 7.0, and 7.5. The vulnerability is due to improper handling of crafted HTTP requests with repeated parameters in asp.dll, which can cause excessive stack usage and result in a denial of service (daemon outage). This issue is also known as the 'IIS Repeated Parameter Request Denial of Service Vulnerability.'
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 (1 hidden).
This repository contains a single Metasploit auxiliary module targeting a denial-of-service vulnerability (CVE-2010-1899) in Microsoft IIS 6.0 when serving ASP pages. The exploit works by repeatedly sending large HTTP HEAD requests with a massive POST payload to a specified ASP page, causing stack exhaustion and making the IIS service unresponsive until it is manually restarted. The module is written in Ruby and leverages Metasploit's auxiliary and DoS mixins. It requires the attacker to specify the target host, port (default 80), and the URI of an ASP page (default '/page.asp'). The exploit is a proof-of-concept and does not provide shell access or code execution, only denial of service. The only file in the repository is the Metasploit module itself, and it is structured with standard Metasploit options and methods.
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.