Incorrect Default Permissions in keyring

published 2019-10-28 7 y ago modified 2026-06-16 4 mo ago also GHSA-p86x-652p-6385 , PYSEC-2019-181 , EUVD-2019-0070

cvss: 7.5; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 1.8%; EPSS 1.8% chance of exploitation in 30 days, percentile 79%
public exploits: 0; none known

Python keyring lib before 0.10 created keyring files with world-readable permissions.

Patch / fix

fixed in 2 distros 1 links 1

pypi keyring 0.10
python keyring 0.10

python-keyring Debian 14, Debian 13, Debian 12 0.9.2-1.1

debian advisories DEBIAN-CVE-2012-5577

bitbucket.org/kang/python-keyring-lib@049cd18 commit

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2012-5577 updated 2025-11-21 cvss 2.1

python-keyring: insecure permissions on configuration file

Red Hat All currently supported Red Hat products
not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.84% chance of exploitation in the next 30 days, higher than 79% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	3.1	7.5	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
NVD	2.0	5.0	AV:N/AC:L/Au:N/C:P/I:N/A:N
GitHub	3.1	7.5	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem	package	affected	fixed in
pypi	keyring	<0.10	0.10

Affected products

Python keyring lib Python keyring lib

Classification

Weakness

CWE-276 Incorrect Default Permissions

References

bitbucket.org /kang/python-keyring-lib/commits/049cd181470f1ee6c540e1d64acf1def7b1de0c1
web, patch, third-party-advisory
security-tracker.debian.org /tracker/CVE-2012-5577
web, third-party-advisory
bugzilla.redhat.com /show_bug.cgi?id=CVE-2012-5577
web, issue-tracking, third-party-advisory, report
openwall.com /lists/oss-security/2012/11/27/3
web, mailing-list, third-party-advisory
bitbucket.org /kang/python-keyring-lib/issue/67/set-go-rwx-on-keyring_passcfg
web, permissions-required
nvd.nist.gov /vuln/detail/CVE-2012-5577
advisory
bitbucket.org /kang/python-keyring-lib
package
github.com /advisories/GHSA-p86x-652p-6385
advisory
github.com /pypa/advisory-database/tree/main/vulns/keyring/PYSEC-2019-181.yaml
web

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary