medium5.8Public exploit code
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 r…
Public exploit code
Working exploit or proof of concept code has been published for this vulnerability. Treat unpatched systems as at risk.
- Privoxy Proxy - Authentication Information Disclosure2013-03-11 · webapps · php · Verified
Impact
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
| Vendor | Product | Affected versions |
|---|---|---|
| Privoxy | Privoxy | through 3.0.20 Versions 2.9.0, 2.9.1, 2.9.2, 2.9.3, 2.9.11 |
Weakness classification
References
- NVD record
- CVE.org record
- http://blog.c22.cc/2013/03/11/privoxy-proxy-authentication-credential-exposure-cve-2013-2503/
- 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/
- http://ijbswa.cvs.sourceforge.net/viewvc/ijbswa/current/ChangeLog?revision=1.188&view=markup
- http://lists.opensuse.org/opensuse-updates/2013-03/msg00118.html