How severe is CVE-2012-4571?

CVE-2012-4571 has a CVSS 2.0 base score of 2.1, rated low severity.

Is CVE-2012-4571 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (29th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2012-4571?

CVE-2012-4571 affects Python Keyring. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2012-4571?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2012-4571 published?

CVE-2012-4571 was published on 2012-11-30 and last updated on 2026-06-16.

CVE-2012-4571

CVE-2012-4571 is a low-severity vulnerability in Python Keyring with a CVSS 2.0 base score of 2.1. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-310.

Key facts

Severity: Low (CVSS 2.0 base score 2.1)
EPSS exploit prediction: 0% (29th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-310
Affected product: Python Keyring
Published: 2012-11-30
Last modified: 2026-06-16

Description

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.

Frequently asked questions

What is 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.
How severe is CVE-2012-4571?: CVE-2012-4571 has a CVSS 2.0 base score of 2.1, rated low severity.
Is CVE-2012-4571 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (29th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2012-4571?: CVE-2012-4571 affects Python Keyring. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2012-4571?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2012-4571 published?: CVE-2012-4571 was published on 2012-11-30 and last updated on 2026-06-16.

References

Affected products (1)

cpe:2.3:a:python:keyring:0.9.1:*:*:*:*:*:*:*

More vulnerabilities in Python Keyring

CVE-2012-5577 — High (CVSS 7.5): Python keyring lib before 0.10 created keyring files with world-readable permissions.
CVE-2012-5578 — Medium (CVSS 6.2): Python keyring has insecure permissions on new databases allowing world-readable files to be created

All CVEs affecting Python Keyring →

Other CWE-310 (Cryptographic Issues) vulnerabilities

CVE-2014-7878 — Critical (CVSS 10.0): The Application Lifecycle Service (ALS) in HP Helion Cloud Development Platform 1.0, when a virtual machine is derived…
CVE-2013-3712 — Critical (CVSS 10.0): SUSE Studio Onsite 1.3.x before 1.3.6 and SUSE Studio Extension for System z 1.3 uses "static" secret tokens, which has…
CVE-2013-6952 — Critical (CVSS 10.0): The Belkin WeMo Home Automation firmware before 3949 has a hardcoded GPG key, which makes it easier for remote…
CVE-2013-6838 — Critical (CVSS 10.0): An unspecified Enghouse Interactive Professional Services "addon product" in Enghouse Interactive IVR Pro (VIP2000)…
CVE-2013-0137 — Critical (CVSS 10.0): The default configuration of the Digital Alert Systems DASDEC EAS device before 2.0-2 and the Monroe Electronics R189…
CVE-2011-5123 — Critical (CVSS 10.0): The Antivirus component in Comodo Internet Security before 5.3.175888.1227 does not check whether X.509 certificates in…

Browse all CWE-310 (Cryptographic Issues) vulnerabilities →