VDB
CVE-2013-2503
CVE-2013-2503
PUBLISHED
Reported by mitre · Published March 11, 2013
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.
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| privoxy | privoxy | 3.0.20 |
Affected products
| Vendor | Product | Versions |
|---|---|---|
| n/a | n/a | n/a |
| n/a | n/a | * |
Timeline
- Mar 11, 2013 PoC Published
- Mar 11, 2013 CVE Published
- Feb 4, 2022 EPSS Score (30 in total, the first dated here)
- Apr 5, 2026 Security Advisory (2 in total, the first dated here)
- Apr 29, 2026 CVE Updated
- Oct 24, 2026 Coalition ESS Score
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2013-2503
vulnetix vdb fixes CVE-2013-2503
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2013-2503/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart
References
- x_refsource_MISC
- x_refsource_CONFIRM
- openSUSE-SU-2013:0564 vendor-advisoryx_refsource_SUSE