Back to Database
Status published
Medium
CVE-2013-2503
Privoxy before 3.0.21 does not properly handle Proxy-Authenticate and Proxy-Authorization...
Vulnerability Description
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.
Impact Analysis
Refer to official advisory for detailed impact metrics.
Remediation
Ensure systems are updated to the latest vendor-supplied patch levels.
THREAT MONITOR
Am I Vulnerable?
Launch our assessment wizard to check if your infrastructure is exposed to • CVE-2013-2503
Credits & Attribution
No credits recorded in the NVD database.
References
More from privoxy
View All →CVE-2016-1983
The client_host function in parsers.c in Privoxy before 3.0.24 allows...
High
7.5
CVE-2016-1982
The remove_chunked_transfer_coding function in filters.c in Privoxy before 3.0.24 allows...
High
7.5
CVE-2015-1380
jcc.c in Privoxy before 3.0.23 allows remote attackers to cause...
Medium
5
CVE-2015-1201
Privoxy before 3.0.22 allows remote attackers to cause a denial...
Medium
5
CVE-2015-1031
Multiple use-after-free vulnerabilities in Privoxy before 3.0.22 allow remote attackers...
High
7.5
Affected Vendor
privoxy
View all reports →Affected Software
privoxy
Vulnerable Versions:
0, 2.9.0, 2.9.1, 2.9.2, 2.9.3, 2.9.11, 2.9.12, 2.9.13, 2.9.14, 2.9.16, 2.9.18, 3.0, 3.0.2, 3.0.3, 3.0.5, 3.0.6, 3.0.7, 3.0.8, 3.0.9, 3.0.10, 3.0.11, 3.0.12, 3.0.13, 3.0.14, 3.0.15, 3.0.16, 3.0.17, 3.0.18, 3.0.19
Timeline
Official Publish:
March 11th, 2013
Last Modified:
August 6th, 2024
Added to House:
July 19th, 2026
CVSS Vectors
Weaknesses (CWE)
No CWE data available
MITRE ATT&CK TTPs
No associated TTPs found for this vulnerability.