Upstream information
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.SUSE information
Overall state of this security issue: Does not affect SUSE products
This issue is currently rated as having moderate severity.
| CVSS detail | National Vulnerability Database | SUSE | 
|---|---|---|
| Base Score | 5.8 | 5.8 | 
| Vector | AV:N/AC:M/Au:N/C:P/I:P/A:N | AV:N/AC:M/Au:N/C:P/I:P/A:N | 
| Access Vector | Network | Network | 
| Access Complexity | Medium | Medium | 
| Authentication | None | None | 
| Confidentiality Impact | Partial | Partial | 
| Integrity Impact | Partial | Partial | 
| Availability Impact | None | None | 
SUSE Security Advisories:
- openSUSE-SU-2013:0564-1
SUSE Timeline for this CVE
CVE page created: Fri Jun 28 13:32:19 2013CVE page last modified: Mon Oct 6 18:19:09 2025
