CVE-2012-5578: PYSEC-2019-182 - Python keyring has insecure permissions on new databases allowing world-readable files to be created

CVE-2012-5578 · Severity: low · CVSS 3.1 · Published 2019-11-25

Python keyring has insecure permissions on new databases allowing world-readable files to be created

Technologies: keyring (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2012-5578 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2012-5578 being exploited in the wild.
How severe is CVE-2012-5578?
Low severity, with a CVSS score of 3.1, published 25 November 2019.
Which products and versions are affected?
keyring (PyPI) ECOSYSTEM:introduced=0,fixed=0.10, ECOSYSTEM:introduced=0,fixed=0.10.1.
Is there a fix for CVE-2012-5578?
Yes. keyring (PyPI): upgrade to 0.10, 0.10.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2012-5578?
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.10, 0.10.1 or later
    pip install "keyring>=0.10.1"

Affected products

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

Identifiers

  • CVE-2012-5578
  • GHSA-8867-vpm3-g98g
  • PYSEC-2019-182

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