Breaking News: Hijacked Releases of Microsoft’s Official agent-framework Steals Azure and CI Credentials
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2012-3499

httpd: multiple XSS flaws due to unescaped hostnames

Overview

Published
26 Feb 2013
Modified
29 Apr 2026
Medium CVE
0 Registry packages
9 OS packages
4 Linux distributions
Yes Fix available

Description

Multiple cross-site scripting (XSS) vulnerabilities in the Apache HTTP Server 2.2.x before 2.2.24-dev and 2.4.x before 2.4.4 allow remote attackers to inject arbitrary web script or HTML via vectors involving hostnames and URIs in the (1) mod_imagemap, (2) mod_info, (3) mod_ldap, (4) mod_proxy_ftp, and (5) mod_status modules.

Source: OX vulnerability database

Severity

4.3 · MEDIUM

CVSS 2.0 base score, scored by NVD.

Access vector
Network
Access complexity
Medium
Authentication
None
Confidentiality
None
Integrity
Partial
Availability
None

AV:N/AC:M/Au:N/C:N/I:P/A:N

Weakness: CWE-79

Affected packages · 0

No registry package. This ID affects operating system packages only.

Operating systems · 8 fixes

debian 4 releases · 1 package

fixed 4
apache2
debian fixes for CVE-2012-3499
ReleasePackageFixed in
11 apache2 2.2.22-13
12 apache2 2.2.22-13
13 apache2 2.2.22-13
14 apache2 2.2.22-13

echo 1 release · 1 package

fixed 1
apache2
echo fixes for CVE-2012-3499
ReleasePackageFixed in
apache2 2.2.22-13

openSUSE 1 release · 1 package

fixed 1
apache2
openSUSE fixes for CVE-2012-3499
ReleasePackageFixed inAdvisory
Tumbleweed apache2 +7 2.4.23-4.1 openSUSE-SU-2024:10268-1

root.io debian 2 releases · 1 package

fixed 2
rootio-apache2
root.io debian fixes for CVE-2012-3499
ReleasePackageFixed in
12 rootio-apache2 2.2.22-13
13 rootio-apache2 2.2.22-13

References

Show all 45 references

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.