Loading vulnerability…
Microsoft Internet Information Services (IIS) 5.x and 6.x determine a file's effective extension using only the portion of the filename that appears before a semicolon (';'). This parsing behavior can be abused to bypass extension restrictions enforced by third-party upload applications or similar validation logic. An attacker can supply a filename such as .asp;.jpg, .cer;.jpg, or .asa;.jpg so that the application accepts the file based on the trailing benign-looking extension, while IIS maps and processes the file according to the dangerous leading extension via handlers such as asp.dll. In practice, this creates a discrepancy between the upload application's validation logic and IIS's interpretation of the same filename, enabling execution of uploaded active content.
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.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
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.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A specific Microsoft IIS ASP multiple extensions security bypass vulnerability referenced in the context of file upload extension bypass techniques.
A referenced IIS multiple-extensions security bypass vulnerability related to file upload and extension parsing weaknesses.
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.