CVE-2012-4571: Python Keyring does not securely initialize encryption cipher

CVE-2012-4571 · Severity: low · CVSS 3.1 · Published 2012-11-30

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.

Technologies: keyring (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2012-4571 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2012-4571 being exploited in the wild.
How severe is CVE-2012-4571?
Low severity, with a CVSS score of 3.1, published 30 November 2012.
Which products and versions are affected?
keyring (PyPI) ECOSYSTEM:introduced=0,fixed=0.9.2.
Is there a fix for CVE-2012-4571?
Yes. keyring (PyPI): upgrade to 0.9.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2012-4571?
Check whether you run keyring (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • keyring (PyPI): upgrade to 0.9.2 or later
    pip install "keyring>=0.9.2"

Affected products

  • keyring (PyPI) ECOSYSTEM:introduced=0,fixed=0.9.2

Identifiers

  • CVE-2012-4571
  • GHSA-p3h7-3c45-qj4v
  • PYSEC-2012-8

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.