# CVE-2012-5578: Incorrect Default Permissions in keyring

> Local attackers can read stored credentials because the Python keyring library creates database files with world-readable permissions.

- **Severity:** Medium 6.2 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Nov 2019
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2012-5578, GHSA-8867-vpm3-g98g, PYSEC-2019-182

## What is CVE-2012-5578?

CVE-2012-5578 is a medium-severity vulnerability in Python keyring, published on 25 Nov 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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

Weakness: CWE-276 (Incorrect Default Permissions)

## Which versions are affected by CVE-2012-5578?

3 open source packages ship an affected version, including keyring. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `keyring` | PyPI | All versions | 0.10 |
| `keyring` | PyPI | All versions | 0.10 |
| `keyring` | PyPI | All versions | 0.10.1 |

Products: Python Keyring.

## How do I fix CVE-2012-5578?

Upgrade keyring to a fixed version for your release line: 0.10 or 0.10.1.

## Is CVE-2012-5578 being exploited?

There is no known exploitation of CVE-2012-5578 in the wild and no public exploit code.

## Other vulnerabilities in Python keyring

- [CVE-2012-4571](https://insights.sbomify.com/CVE-2012-4571/): Python Keyring does not securely initialize encryption cipher (low 2.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-5578 and fix it if it is affected.

What it is: CVE-2012-5578 is a medium-severity vulnerability in Python keyring, published on 25 Nov 2019. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2012-5578 in the wild and no public exploit code.

Affected packages and fixed versions:
- keyring (PyPI): affected all versions; fixed in 0.10
- keyring (PyPI): affected all versions; fixed in 0.10
- keyring (PyPI): affected all versions; fixed in 0.10.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2012-5578/ (Markdown: https://insights.sbomify.com/CVE-2012-5578/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2012-5578
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2012-5578
- OSV: https://osv.dev/vulnerability/CVE-2012-5578

---
From sbomify Insights: https://insights.sbomify.com/CVE-2012-5578/
Summaries are generated and may contain mistakes; the official description above is the record.