Skip to content
Fencer Intel
high 7.5

CVE-2012-4571 json

Python Keyring does not securely initialize encryption cipher

published 2012-11-30 13 y ago modified 2026-06-16 4 mo ago also GHSA-p3h7-3c45-qj4v , PYSEC-2012-8 , EUVD-2012-0012

cvss
7.5
version 3.1, GitHub
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 31%
public exploits
0
none known

Summary

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.

Patch / fix

  • pypi keyring 0.9.2
  • python-keyring Debian 14, Debian 13, Debian 12 0.9.2-1

debian advisories DEBIAN-CVE-2012-4571

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2012-4571 updated cvss 2.1

python-keyring: weak encryption in keyring

  • Red Hat OpenStack Platform 3 python-keyring Red Hat OpenStack Platform 4 python-keyring
    affected: no fix planned “Will not fix”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.37% chance of exploitation in the next 30 days, higher than 31% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 2.1 AV:L/AC:L/Au:N/C:P/I:N/A:N
GitHub 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
pypi keyring
<0.9.2
0.9.2

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.