How severe is CVE-2011-3368?

No CVSS score has been assigned to CVE-2011-3368 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2011-3368?

Affected package information for CVE-2011-3368 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2011-3368?

No fixed release is recorded for CVE-2011-3368 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.

How do I detect CVE-2011-3368 in my code and dependencies?

Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).

How do I mitigate CVE-2011-3368 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2011-3368 actively exploited in the wild?

Yes. There are 4 known exploit references for CVE-2011-3368, including 1 documented proof-of-concept exploit on Exploit-DB and 3 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2011-3368?

CVE-2011-3368 has an EPSS (Exploit Prediction Scoring System) score of 90.7%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is CVE-2011-3368?

CVE-2011-3368 is classified as Improper Input Validation (CWE-20). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2011-3368 published, and has it been updated?

CVE-2011-3368 was published on October 5, 2011 and was last updated on April 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

Not in CISA KEV

CVE-2011-3368 — Red Hat

CVE-2011-3368 is a Improper Input Validation vulnerability. 4 public exploit references exist, so weaponization risk is real. No vendor fix is recorded yet; mitigation options are listed below.

Published

Oct 5, 2011

Updated

Apr 10, 2026

Affected

1 product

Patched

See advisory

Exploits

4 known

Exploitation data as of Oct 28, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

90.7%probability of exploitation in next 30 days

Very High Risk0.00%

Lower risk than most CVEs100th percentile — riskier than 100% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Description

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 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 initial @ (at sign) character.

Affected Products

1 product · 100 configurations

Application

http serverapache

98 versions

1.31.3.01.3.11.3.1.11.3.21.3.31.3.41.3.51.3.61.3.71.3.81.3.9

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-17969remotemultiple✓ Verified

Apache mod_proxy - Reverse Proxy Exposure

by Rodrigo Marcos · Oct 11, 2011

Exploit-DB Source

Detection & mitigation playbook

Vulnerability

Detect
Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).
Remediation status
No fixed release is recorded for CVE-2011-3368 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Product	Fixed in	Advisory
Red Hat Enterprise Linux 4	`httpd-0:2.0.52-49.ent`	RHSA-2011:1392
Red Hat Enterprise Linux 6	`httpd-0:2.2.15-9.el6_1.3`	RHSA-2011:1391
Red Hat JBoss Enterprise Web Server 1 for RHEL 5	`httpd-0:2.2.17-15.4.ep5.el5`	RHSA-2012:0542
Red Hat JBoss Web Server 1.0	see advisory	RHSA-2012:0543

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2011-3368 in your dependencies?

Find it across , including transitive dependencies.

Scan my dependencies How O3 SCA works