Loading vulnerability…
Microsoft Internet Information Services (IIS), when used with certain third-party file upload applications, can allow a remote attacker to bypass extension-based upload restrictions by abusing NTFS Alternate Data Streams (ADS) filename syntax. A crafted filename containing a dangerous extension before a colon and an allowed extension after it, such as .asp:.jpg, may be accepted by the upload application as a safe image upload while IIS/NTFS processing results in creation of an empty file with the dangerous extension, such as an empty .asp file. The issue arises from incorrect validation of the filename by the upload component and IIS support for ADS semantics on NTFS. The available information indicates this is related to unrestricted or improperly restricted file upload handling; however, the note in the source indicates the root cause may reside in the third-party upload application rather than IIS itself.
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 CVE referenced in the file upload security bypass reference list, but not described in detail in the content.
A referenced IIS/ASP multiple-extensions security bypass vulnerability associated with dangerous file upload handling and execution bypass scenarios.
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.