Skip to main content
Mallory
MediumVulnerability

CVE-2011-3639: Apache HTTP Server mod_proxy Reverse-Proxy SSRF

Published Nov 30, 2011 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS4.3Medium · v2
EPSS49.7%99th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Apache Software Foundation
IdentifiersCVE-2011-3639CWE-918

CVE-2011-3639 is an incomplete-fix vulnerability in Apache HTTP Server mod_proxy affecting Apache HTTP Server 2.0.x through 2.0.64 and 2.2.x before 2.2.18 when the Revision 1179239 patch for CVE-2011-3368 is present. The flaw arises from improper interaction between reverse-proxy configuration using RewriteRule or ProxyPassMatch pattern matching and HTTP/0.9 requests containing a malformed URI that begins with an at-sign character. An unauthenticated remote client can cause the reverse proxy to forward requests to intranet hosts.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

An external attacker can use the affected server as a server-side request forgery proxy to issue requests to internal or otherwise network-restricted servers. This can expose internal services to attacker-controlled requests and may enable access to internal resources reachable by the Apache server.

Mitigation

If you can’t patch tonight, do this now.

Until patched, avoid or restrict vulnerable reverse-proxy configurations that use RewriteRule or ProxyPassMatch pattern matching. Enforce rejection of HTTP/0.9 requests and malformed request targets at the edge, and limit the reverse proxy's network access to internal destinations using network segmentation and egress filtering.

Remediation

Patch, then assume compromise.

Upgrade Apache HTTP Server to version 2.2.18 or a vendor-supported release containing the fix for CVE-2011-3639. Apache HTTP Server 2.0.x is end of life; migrate to a supported release and apply the vendor-provided security update.

Public exploits

Exploits

No validated public exploits yet. Hidden: 1 not yet analyzed, such as Exploit-DB entries.

View more in app →
Candidate exploits are awaiting analysis. View them in Mallory.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Apache Software FoundationApache HTTP Serverapplication
Apache Software FoundationHttp Server2.0a1application
Apache Software FoundationHttp Server2.0a2application
Apache Software FoundationHttp Server2.0a3application
Apache Software FoundationHttp Server2.0a4application
Apache Software FoundationHttp Server2.0a5application
Apache Software FoundationHttp Server2.0a6application
Apache Software FoundationHttp Server2.0a7application
Apache Software FoundationHttp Server2.0a8application
Apache Software FoundationHttp Server2.0a9application
FAQ

Frequently asked questions

Is CVE-2011-3639 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2011-3639 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2011-3639?
As of Oct 16, 2026, Mallory has not confirmed a public exploit for CVE-2011-3639. 1 candidate exploit record is not yet analyzed.
Is there a patch for CVE-2011-3639?
Upgrade Apache HTTP Server to version 2.2.18 or a vendor-supported release containing the fix for CVE-2011-3639. Apache HTTP Server 2.0.x is end of life; migrate to a supported release and apply the vendor-provided security update.
What products are affected by CVE-2011-3639?
Apache Software Foundation Apache HTTP Server, Apache Software Foundation Http Server2.0a1, Apache Software Foundation Http Server2.0a2, Apache Software Foundation Http Server2.0a3, Apache Software Foundation Http Server2.0a4, and 5 more.
How severe is CVE-2011-3639?
CVE-2011-3639 has a CVSS v2 score of 4.3 (Medium) and an EPSS score of 49.7% (99th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

1 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.