CVE-2013-2503 · cross-distro fix matrix

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 remote HTTP servers to spoof the intended proxy service via a 407 (aka Proxy Authentication Required) HTTP status code.

Affects 3 Linux releases across 3 (distro × package) combinations.

Fix per ecosystem

Each block below is a distro release where CVE-2013-2503 has a known fix. Run the listed command on that distro to remediate.

Debian bullseye

Source: Debian Security Tracker

privoxy→ fixed in3.0.21-1urgency: low

sudo apt-get install --only-upgrade -y privoxy

Debian bookworm

Source: Debian Security Tracker

privoxy→ fixed in3.0.21-1urgency: low

sudo apt-get install --only-upgrade -y privoxy

Debian trixie

Source: Debian Security Tracker

privoxy→ fixed in3.0.21-1urgency: low

sudo apt-get install --only-upgrade -y privoxy

Are YOU affected by CVE-2013-2503?

5-second check on your actual server. Reads /etc/os-release, uname -r, and the distro's package manager; matches against this same cross-source index live.

curl https://mindsparkstack.com/scan.sh | bash

Form-based quickscan View on NVD

Continuous monitoring beats manual checking

CVE-2013-2503dropped silently in your distro's update channel. Every new CVE is the same story. StackPatch runs the matcher hourly against all 5 sources and emails the exact remediation when something new applies to one of your servers. $99 lifetime, 50 founder seats, 30-day refund.

See StackPatch ($99 lifetime)