Loading vulnerability…
CVE-2019-0220 is an improper path-equivalence vulnerability in Apache HTTP Server 2.4.0 through 2.4.38. When an HTTP request path contains multiple consecutive slash characters, parts of Apache request processing implicitly collapse the repeated slashes while regular-expression-based directives, including LocationMatch and RewriteRule, can evaluate the uncollapsed path. This inconsistent normalization can cause URL matching and authorization or rewrite behavior to differ from administrator expectations.
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.
18 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Apache HTTP Server URL-normalization inconsistency vulnerability.
A URL-normalization inconsistency in Apache HTTP Server (httpd).
An Apache HTTP Server URL-normalization inconsistency vulnerability addressed in the httpd:2.4 update.
An Apache HTTP Server request-normalization inconsistency involving multiple consecutive slashes, which can cause directives such as LocationMatch and RewriteRule to behave unexpectedly.
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.