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…
Does this matter?
Lower severity and a low EPSS score (4.63%). Track it; it rarely justifies an emergency change on its own.
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.
- CVSS 2.0
- 5.8 MEDIUMAV:N/AC:M/Au:N/C:P/I:P/A:N
- EPSS
- 4.63% probability · 91th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-20
- Affected
- privoxy/privoxy
- Source
- cve@mitre.org
References
- http://blog.c22.cc/2013/03/11/privoxy-proxy-authentication-credential-exposure-cve-2013-2503/Exploit
- http://ijbswa.cvs.sourceforge.net/viewvc/ijbswa/current/ChangeLog?revision=1.188&view=markup
- http://lists.opensuse.org/opensuse-updates/2013-03/msg00118.html
- http://blog.c22.cc/2013/03/11/privoxy-proxy-authentication-credential-exposure-cve-2013-2503/Exploit
- http://ijbswa.cvs.sourceforge.net/viewvc/ijbswa/current/ChangeLog?revision=1.188&view=markup
- http://lists.opensuse.org/opensuse-updates/2013-03/msg00118.html
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.