Vulnerability Monitor

The vendors, products, and vulnerabilities you care about

CVE-2013-2503

Privoxy before 3.0.21 does not properly handle Proxy-Authenticate and Proxy-Authorization headers in the client-server data stream, which makes it easier for remote HTTP servers to spoof the intended proxy service via a 407 (aka Proxy Authentication Required) HTTP status code.

Security Impact Summary

CVE-2013-2503 is a security vulnerability that . Impacting 1 product from privoxy organizations running these solutions should prioritize assessment and patching.

Historical Context

Documented in 2013, this vulnerability occurred amid the cloud computing expansion era, where traditional network perimeter security models were being reevaluated. Organizations were transitioning from isolated infrastructure to interconnected systems, creating new attack surfaces that vulnerabilities like this could exploit.

Published

2013-03-11T17:55:01.830

Last Modified

2025-04-11T00:51:21.963

Status

Deferred

Source

[email protected]

Severity

CVSSv2: 5.8 (MEDIUM)

CVSSv2 Vector

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

Access Vector: NETWORK
Access Complexity: MEDIUM
Authentication: NONE
Confidentiality Impact: PARTIAL
Integrity Impact: PARTIAL
Availability Impact: NONE

Exploitability Score

8.6

Impact Score

4.9

Weaknesses

Type: Primary
CWE-20

Affected Vendors & Products

Type	Vendor	Product	Version/Range	Vulnerable?
Application	privoxy	privoxy	≤ 3.0.20	Yes
Application	privoxy	privoxy	2.9.0	Yes
Application	privoxy	privoxy	2.9.1	Yes
Application	privoxy	privoxy	2.9.2	Yes
Application	privoxy	privoxy	2.9.3	Yes
Application	privoxy	privoxy	2.9.11	Yes
Application	privoxy	privoxy	2.9.11	Yes
Application	privoxy	privoxy	2.9.11	Yes
Application	privoxy	privoxy	2.9.12	Yes
Application	privoxy	privoxy	2.9.13	Yes
Application	privoxy	privoxy	2.9.14	Yes
Application	privoxy	privoxy	2.9.16	Yes
Application	privoxy	privoxy	2.9.18	Yes
Application	privoxy	privoxy	3.0	Yes
Application	privoxy	privoxy	3.0.2	Yes
Application	privoxy	privoxy	3.0.3	Yes
Application	privoxy	privoxy	3.0.5	Yes
Application	privoxy	privoxy	3.0.6	Yes
Application	privoxy	privoxy	3.0.7	Yes
Application	privoxy	privoxy	3.0.8	Yes
Application	privoxy	privoxy	3.0.9	Yes
Application	privoxy	privoxy	3.0.10	Yes
Application	privoxy	privoxy	3.0.11	Yes
Application	privoxy	privoxy	3.0.12	Yes
Application	privoxy	privoxy	3.0.13	Yes
Application	privoxy	privoxy	3.0.14	Yes
Application	privoxy	privoxy	3.0.15	Yes
Application	privoxy	privoxy	3.0.16	Yes
Application	privoxy	privoxy	3.0.17	Yes
Application	privoxy	privoxy	3.0.18	Yes
Application	privoxy	privoxy	3.0.19	Yes

References

http://blog.c22.cc/2013/03/11/privoxy-proxy-authentication-credential-exposure-cve-2013-2503/ Exploit ([email protected])
http://ijbswa.cvs.sourceforge.net/viewvc/ijbswa/current/ChangeLog?revision=1.188&view=markup ([email protected])
http://lists.opensuse.org/opensuse-updates/2013-03/msg00118.html ([email protected])
http://blog.c22.cc/2013/03/11/privoxy-proxy-authentication-credential-exposure-cve-2013-2503/ Exploit (af854a3a-2127-422b-91ae-364da2661108)
http://ijbswa.cvs.sourceforge.net/viewvc/ijbswa/current/ChangeLog?revision=1.188&view=markup (af854a3a-2127-422b-91ae-364da2661108)
http://lists.opensuse.org/opensuse-updates/2013-03/msg00118.html (af854a3a-2127-422b-91ae-364da2661108)

How SecUtils Interprets This CVE

SecUtils normalizes and enriches National Vulnerability Database (NVD) records by standardizing vendor and product identifiers, aggregating vulnerability metadata from both NVD and MITRE sources, and providing structured context for security teams. For privoxy's affected products, we extract Common Platform Enumeration (CPE) data, Common Weakness Enumeration (CWE) classifications, CVSS severity metrics, and reference data to enable rapid vulnerability prioritization and asset correlation. This record contains no exploit code, proof-of-concept instructions, or attack methodologies—only defensive intelligence necessary for patch management, risk assessment, and security operations.