{"answers":{"affected":"3 open source packages ship an affected version, including keystone. It affects 1 product.","exploited":"There is no known exploitation of CVE-2012-4413 in the wild and no public exploit code.","fix":"Upgrade keystone to 2012.1.3 or later.","what":"CVE-2012-4413 is a medium-severity vulnerability in n/a, published on 18 Sep 2012. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2012-4413 and fix it if it is affected.\n\nWhat it is: CVE-2012-4413 is a medium-severity vulnerability in n/a, published on 18 Sep 2012. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2012-4413 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- keystone (PyPI): affected all versions; fixed in 2012.1.3\n- keystone (PyPI): affected all versions; fixed in 2012.1.3\n- keystone (PyPI): affected all versions; fixed in 2012.1.3\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-4413/ (Markdown: https://insights.sbomify.com/CVE-2012-4413/index.md)","id":"CVE-2012-4413","markdown":"https://insights.sbomify.com/CVE-2012-4413/index.md","name":"CVE-2012-4413","record":{"aliases":["DEBIAN-CVE-2012-4413","GHSA-mrxv-65rv-6hxq","PYSEC-2026-833"],"analysis":{"component_type":"cloud_service","fix_type":"upgrade","impacts":["privilege_escalation","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"OpenStack Identity","requires_auth":"low_privilege","summary":"Authenticated users retain revoked role privileges because tokens are not invalidated, allowing unauthorized access to resources.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"keystone","vendor":"openstack"}],"cvss":{"score":4,"severity":"medium","source":"nvd","vector":"AV:N/AC:L/Au:S/C:N/I:P/A:N","version":"2.0"},"cwes":[{"id":"CWE-264","name":null}],"description":"OpenStack Keystone 2012.1.3 does not invalidate existing tokens when granting or revoking roles, which allows remote authenticated users to retain the privileges of the revoked roles.","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":"OpenStack Keystone does not invalidate existing tokens when granting or revoking roles","id":"CVE-2012-4413","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"security_feature_bypass","year":"2012"},"n_packages":3,"n_references":7,"next":{"headline":"SQL injection in n/a","id":"CVE-2012-4414"},"packages":[{"ecosystem":"PyPI","fixed":["2012.1.3"],"introduced":["0"],"last_affected":[],"package":"keystone","purl":null,"source":"GHSA-mrxv-65rv-6hxq"},{"ecosystem":"PyPI","fixed":["2012.1.3"],"introduced":["0"],"last_affected":[],"package":"keystone","purl":"pkg:pypi/keystone","source":"GHSA-mrxv-65rv-6hxq"},{"ecosystem":"PyPI","fixed":["2012.1.3"],"introduced":["0"],"last_affected":[],"package":"keystone","purl":"pkg:pypi/keystone","source":"PYSEC-2026-833"}],"prev":{"headline":"Integer overflow in n/a","id":"CVE-2012-4412"},"products":["n/a"],"published":"2012-09-18","related":[{"cvss_score":8.8,"headline":"Insufficient Session Expiration in OpenStack Keystone","id":"CVE-2020-12690","kev_date_added":null,"published":"2020-05-06"},{"cvss_score":8.8,"headline":"OpenStack Keystone Credential Leakage","id":"CVE-2019-19687","kev_date_added":null,"published":"2019-12-09"},{"cvss_score":7.9,"headline":"OpenStack Keystone has an Incorrect Authorization Issue","id":"CVE-2026-43001","kev_date_added":null,"published":"2026-05-01"},{"cvss_score":7.8,"headline":"OpenStack Identity (Keystone) DoS through V3 API authentication chaining","id":"CVE-2014-2828","kev_date_added":null,"published":"2014-04-15"},{"cvss_score":7.5,"headline":"OpenStack Keystone allows information disclosure during account locking","id":"CVE-2021-38155","kev_date_added":null,"published":"2021-08-06"},{"cvss_score":7.5,"headline":"OpenStack Identity Keystone and keystonemiddleware Insufficiently Protected Credentials","id":"CVE-2015-7546","kev_date_added":null,"published":"2016-02-03"},{"cvss_score":7.5,"headline":"OpenStack Keystone Improper Authentication vulnerability","id":"CVE-2012-4456","kev_date_added":null,"published":"2012-10-09"}],"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":["n/a"]},"summary":"Authenticated users retain revoked role privileges because tokens are not invalidated, allowing unauthorized access to resources.","url":"https://insights.sbomify.com/CVE-2012-4413/"}