{"answers":{"affected":"3 open source packages ship an affected version, including keyring. It affects 1 product.","exploited":"There is no known exploitation of CVE-2012-5578 in the wild and no public exploit code.","fix":"Upgrade keyring to a fixed version for your release line: 0.10 or 0.10.1.","what":"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."},"fix_prompt":"Check this codebase for CVE-2012-5578 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2012-5578 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- keyring (PyPI): affected all versions; fixed in 0.10\n- keyring (PyPI): affected all versions; fixed in 0.10\n- keyring (PyPI): affected all versions; fixed in 0.10.1\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2012-5578/ (Markdown: https://insights.sbomify.com/CVE-2012-5578/index.md)","id":"CVE-2012-5578","markdown":"https://insights.sbomify.com/CVE-2012-5578/index.md","name":"CVE-2012-5578","record":{"aliases":["DEBIAN-CVE-2012-5578","GHSA-8867-vpm3-g98g","PYSEC-2019-182"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Python keyring library","requires_auth":"none","summary":"Local attackers can read stored credentials because the Python keyring library creates database files with world-readable permissions.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"keyring","vendor":"python"}],"cvss":{"score":6.2,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-276","name":"Incorrect Default Permissions"}],"description":"Python keyring has insecure permissions on new databases allowing world-readable files to be created","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Incorrect Default Permissions in keyring","id":"CVE-2012-5578","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"information_disclosure","year":"2012"},"n_packages":3,"n_references":6,"next":{"headline":"Code injection in n/a","id":"CVE-2012-5580"},"packages":[{"ecosystem":"PyPI","fixed":["0.10"],"introduced":["0"],"last_affected":[],"package":"keyring","purl":null,"source":"GHSA-8867-vpm3-g98g"},{"ecosystem":"PyPI","fixed":["0.10"],"introduced":["0"],"last_affected":[],"package":"keyring","purl":"pkg:pypi/keyring","source":"GHSA-8867-vpm3-g98g"},{"ecosystem":"PyPI","fixed":["0.10.1"],"introduced":["0"],"last_affected":[],"package":"keyring","purl":"pkg:pypi/keyring","source":"PYSEC-2019-182"}],"prev":{"headline":"Incorrect Default Permissions in keyring","id":"CVE-2012-5577"},"products":["Python keyring"],"published":"2019-11-25","related":[{"cvss_score":2.1,"headline":"Python Keyring does not securely initialize encryption cipher","id":"CVE-2012-4571","kev_date_added":null,"published":"2012-11-30"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-06","vendors":["Python"]},"summary":"Local attackers can read stored credentials because the Python keyring library creates database files with world-readable permissions.","url":"https://insights.sbomify.com/CVE-2012-5578/"}