CVE-2014-5277 · cross-distro fix matrix

CVE-2014-5277: Docker before 1.3.1 and docker-py before 0.5.3 fall back to HTTP when the HTTPS connection to the registry fails, which allows man-in-the-middle attackers to conduct downgrade attacks and obtain authentication and image data by leveraging a network position between the client and the registry to blo

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

Fix per ecosystem

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

Debian bullseye

Source: Debian Security Tracker

docker.io→ fixed in1.3.1~dfsg1-1urgency: not yet assigned
```
sudo apt-get install --only-upgrade -y docker.io
```

Debian bookworm

Source: Debian Security Tracker

docker.io→ fixed in1.3.1~dfsg1-1urgency: not yet assigned
```
sudo apt-get install --only-upgrade -y docker.io
```

Debian trixie

Source: Debian Security Tracker

docker.io→ fixed in1.3.1~dfsg1-1urgency: not yet assigned
```
sudo apt-get install --only-upgrade -y docker.io
```

Are YOU affected by CVE-2014-5277?

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-2014-5277dropped 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)