Loading vulnerability…
CVE-2011-0419 is a stack consumption / resource exhaustion vulnerability in the filename pattern-matching routine fnmatch. In Apache Portable Runtime (APR), the issue exists in the fnmatch implementation in apr_fnmatch.c (APR before 1.4.3) and affects Apache HTTP Server before 2.2.18 via its use of APR. Similar vulnerable fnmatch.c implementations are present in libc on multiple platforms (NetBSD 5.1, OpenBSD 4.8, FreeBSD, Apple Mac OS X 10.6, Oracle Solaris 10, and Android). A context-dependent attacker can trigger excessive stack usage and associated CPU/memory consumption by supplying crafted patterns containing repeated "*?" sequences in the first argument to fnmatch. In Apache httpd, this can be demonstrated against mod_autoindex, where attacker-controlled request paths can be processed through fnmatch during directory indexing, leading to denial of service.
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.
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.