Loading vulnerability…
CVE-2011-4317 is an incomplete fix for CVE-2011-3368 in Apache HTTP Server mod_proxy. In affected Apache HTTP Server 1.3.x through 1.3.42, 2.0.x through 2.0.64, and 2.2.x through 2.2.21 with the Revision 1179239 patch applied, reverse-proxy configurations using RewriteRule or ProxyPassMatch can mishandle malformed request URIs containing @ and : characters in invalid positions. The malformed URI can cause an unintended proxy target interpretation and route a request to an intranet backend not intended to be exposed through the reverse proxy.
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.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An Apache HTTP Server mod_rewrite security issue involving potentially surprising rewrite-rule pattern expansions when request URIs were not constrained to URL-path grammar.
A vulnerability in Apache HTTP Server URL rewriting and proxying where crafted request URIs could cause unintended backend network exposure in certain ProxyPassMatch or RewriteRule configurations.
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.