CVE-2016-3092 is an improper-input-validation denial-of-service vulnerability in Apache Commons FileUpload's MultipartStream multipart parser. Versions before 1.3.2 inefficiently process a multipart boundary whose length is just below the 4,096-byte upload read-buffer size. An attacker can submit a crafted multipart upload request that causes excessive CPU consumption while the parser searches for the boundary. The issue also affects products that bundle vulnerable Commons FileUpload versions, including affected Apache Tomcat releases.
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 valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
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.
24 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Denial-of-service flaw in Apache Commons FileUpload triggered by specially sized multipart boundaries.
A Commons FileUpload multipart-boundary parsing flaw can cause denial of service.
A denial-of-service vulnerability in Commons FileUpload triggered by specially sized multipart upload boundaries.
A denial-of-service vulnerability in Commons FileUpload's multipart-boundary processing.
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.