How severe is CVE-2012-4456?

No CVSS score has been assigned to CVE-2012-4456 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2012-4456?

CVE-2012-4456 affects the following packages: keystone (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2012-4456?

Update keystone to 2012.1.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2012-4456 is resolved across your whole dependency graph.

How do I detect CVE-2012-4456 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for keystone, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2012-4456 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2012-4456?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2012-4456 can be triaged on real exposure rather than presence alone.

Is CVE-2012-4456 actively exploited in the wild?

No public exploit code has been indexed for CVE-2012-4456 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2012-4456?

CVE-2012-4456 has an EPSS (Exploit Prediction Scoring System) score of 4.0%, placing it in the 90th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2012-4456?

CVE-2012-4456 is classified as Improper Authentication (CWE-287). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2012-4456 published, and has it been updated?

CVE-2012-4456 was published on October 9, 2012 and was last updated on July 7, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

Not in CISA KEV

CVE-2012-4456 — keystone

Fix: openstack/keystone@14b136a

CVE-2012-4456 is a Improper Authentication vulnerability in keystone. A fix is available for keystone — see the affected versions and patch details below.

OpenStack Keystone Improper Authentication vulnerability

Also known asGHSA-mf98-r2gf-2x3wPYSEC-2026-832

Published

Oct 9, 2012

Updated

Jul 7, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 17, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

4.0%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs90th percentile — riskier than 90% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

1 pkg affected

🐍keystone

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

The (1) OS-KSADM/services and (2) tenant APIs in OpenStack Keystone Essex before 2012.1.2 and Folsom before folsom-2 do not properly validate X-Auth-Token, which allow remote attackers to read the roles for an arbitrary user or get, create, or delete arbitrary services.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`keystone`	≥ 2012.1&&< 2012.1.2	2012.1.2`pip install --upgrade 'keystone==2012.1.2'`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for keystone, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update keystone to 2012.1.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2012-4456 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2012-4456 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2012-4456. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Product	Fixed in	Advisory
OpenStack Essex for RHEL 6	`openstack-keystone-0:2012.1.2-4.el6`	RHSA-2012:1378

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2012-4456 in your dependencies?

O3 Security finds CVE-2012-4456 across PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works