CVE-2011-3639: n/a vulnerability

CVE-2011-3639: The mod_proxy module in the Apache HTTP Server 2.0.x through 2.0.64 and 2.2.x before 2.2.18, when the Revis...

The mod_proxy module in the Apache HTTP Server 2.0.x through 2.0.64 and 2.2.x before 2.2.18, when the Revision 1179239 patch is in place, does not properly interact with use of (1) RewriteRule and (2) ProxyPassMatch pattern matches for configuration of a reverse proxy, which allows remote attackers to send requests to intranet servers by using the HTTP/0.9 protocol with a malformed URI containing an initial @ (at sign) character. NOTE: this vulnerability exists because of an incomplete fix for CVE-2011-3368.

UnknownCVSS not scoredNot KEV-listedUpdatedAug 6, 2024, 23:37 UTC (UTC+00:00)

Security readout for executives and security teams

This flaw could let an outside user abuse certain legacy Apache reverse proxy configurations to reach internal network servers through the public web server. It matters most where old Apache 2.0 or 2.2 reverse proxies still front intranet systems. The source bundle does not show active exploitation or a CVSS score. Exposure is likely limited to legacy Apache 2.0 or 2.2 reverse proxy deployments using mod_proxy with RewriteRule or ProxyPassMatch pattern-based routing. Modern Apache versions or deployments not using this reverse proxy pattern are not identified as affected in the supplied sources. Prioritize remediation where internet-facing legacy Apache reverse proxies protect internal services. For organizations without Apache 2.0 or 2.2 reverse proxy exposure, urgency is lower. The main business risk is unintended external reachability into intranet resources. Mitigation focus: Identify any Apache 2.0.x or 2.2.x reverse proxies still in service.; Upgrade Apache HTTP Server to a fixed vendor-supported release.; Review Red Hat or Debian advisories if using their packaged Apache builds..

Prepared: Jun 27, 2026, 17:48 UTC (UTC+00:00)

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2011-3639 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup

Vulnerability profileCVE Program record

Severity: Unknown
CVSS: Not scored
Known Exploited: No
Published: Nov 30, 2011, 02:00 UTC (UTC+00:00)

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors

0Timeline events

0ADP providers

2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

CVE List V5 sourceCVE List V5
https://bugzilla.redhat.com/show_bug.cgi?id=752080CVE reference · x_refsource_CONFIRM

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus

n/an/an/aListed

Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.