CVE-2012-4571 · cross-distro fix matrix

CVE-2012-4571: Python Keyring 0.9.1 does not securely initialize the cipher when encrypting passwords for CryptedFileKeyring files, which makes it easier for local users to obtain passwords via a brute-force attack.

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

Fix per ecosystem

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

Debian bullseye

Source: Debian Security Tracker

python-keyring→ fixed in0.9.2-1urgency: not yet assigned
```
sudo apt-get install --only-upgrade -y python-keyring
```

Debian bookworm

Source: Debian Security Tracker

python-keyring→ fixed in0.9.2-1urgency: not yet assigned
```
sudo apt-get install --only-upgrade -y python-keyring
```

Debian trixie

Source: Debian Security Tracker

python-keyring→ fixed in0.9.2-1urgency: not yet assigned
```
sudo apt-get install --only-upgrade -y python-keyring
```

Are YOU affected by CVE-2012-4571?

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-2012-4571dropped 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)