Vulnerabilities · 2013 · Privoxy
CVE-2013-2503
Privoxy vulnerability
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.
Affected products
Privoxy. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Privoxy runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- blog.c22.cc/2013/03/11/privoxy-proxy-authentication-credential-exposure-cve-2013-2503/ · Exploit
- ijbswa.cvs.sourceforge.net/viewvc/ijbswa/current/ChangeLog?revision=1.188&view=markup
- lists.opensuse.org/opensuse-updates/2013-03/msg00118.html
- nvd.nist.gov/vuln/detail/CVE-2013-2503
- cve.org/CVERecord?id=CVE-2013-2503
More vulnerabilities in Privoxy products
CVE-2021-44543CVE-2021-44542CVE-2021-44541CVE-2021-44540CVE-2021-20276CVE-2021-20275CVE-2021-20274CVE-2021-20273All 29
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.