LiveActive security incident?Get immediate response
CVE Record

CVE-2011-4317: The mod_proxy module in the Apache HTTP Server 1.3.x through 1.3.42, 2.0.x through 2.0.64, and 2.2.x throug...

The mod_proxy module in the 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, 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 via a malformed URI containing an @ (at sign) character and a : (colon) character in invalid positions. NOTE: this vulnerability exists because of an incomplete fix for CVE-2011-3368.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

This flaw can let an attacker abuse certain Apache reverse proxy configurations to reach internal servers through the public web server. The issue affects older Apache HTTP Server 1.3, 2.0, and 2.2 releases when a prior patch for CVE-2011-3368 is present but incomplete. Exposure is most likely on legacy Apache HTTP Server reverse proxies using RewriteRule or ProxyPassMatch and running affected 1.3.x, 2.0.x, or 2.2.x versions. Modern deployments are less likely affected, but inherited appliances or vendor-bundled httpd packages need review. Prioritize legacy internet-facing reverse proxies because the business impact is internal network exposure through a public service. If affected systems remain in production, treat remediation as urgent hygiene even without confirmed active exploitation. Mitigation focus: Inventory Apache reverse proxies and confirm httpd version, module use, and proxy rewrite rules.; Apply applicable vendor httpd security updates or follow current vendor guidance.; Review RewriteRule and ProxyPassMatch reverse proxy patterns for unintended internal routing..

Prepared

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-4317 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
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
17Source links

CVSS and timeline data

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

Source materials

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.