CVE Intelligence
Medium Access control

CVE-2012-5571 — Openstack keystone: openstack keystone: authorization bypass via improper ec2 token handling

A flaw was found in OpenStack Keystone. This vulnerability allows remote authenticated users to bypass intended authorization restrictions. This occurs because OpenStack Keystone does not properly handle EC2 (Elastic Compute Cloud) tokens when a user's role has been removed from a tenant. An attacker can leverage a token associated with a removed user role to gain unauthorized access.

Published Dec 17, 2012 · Updated Oct 30, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: redhat

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 2.1% (30-day exploitation probability)+12
  • Technical severity (medium)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
2.06%
ahead of 81% of scored CVEs · Oct 30, 2026
Affects
OpenStack
Essex and 8 more
CVSS base
5.4
Medium · 4 source(s)

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

  • Documented patch — www.openwall.com (NIST National Vulnerability Database)
  • Documented patch — www.openwall.com (NIST National Vulnerability Database)
  • Documented patch — bugs.launchpad.net (NIST National Vulnerability Database)
  • Documented patch — github.com (NIST National Vulnerability Database)
  • Documented patch — github.com (NIST National Vulnerability Database)
  • Documented patch — github.com (NIST National Vulnerability Database)
  • Pip Keystone: fixed in version 8.0.0a0 — github.com (GitHub Security Advisories)

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (OpenStack Essex, OpenStack Folsom, Red Hat OpenStack Essex for RHEL 6…).
  2. Apply the fixed version or the patch documented under Remediation.
  3. Search available logs for exploit probes matching the vulnerability class (access control), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
OpenStack Essex version 2012.1 Vulnerable NIST National Vulnerability Database
OpenStack Folsom version 2012.2 Vulnerable NIST National Vulnerability Database
Red Hat OpenStack Essex for RHEL 6 versions not specified by the source Vulnerable CVE Program (cve.org) e CISA ADP
Red Hat OpenStack Folsom for RHEL 6 versions not specified by the source Vulnerable CVE Program (cve.org) e CISA ADP
Red Hat Red Hat OpenStack Platform 13 (Queens) versions not specified by the source Vulnerable CVE Program (cve.org) e CISA ADP
Red Hat Red Hat OpenStack Platform 16.2 versions not specified by the source Vulnerable CVE Program (cve.org) e CISA ADP
Red Hat Red Hat OpenStack Platform 17.1 versions not specified by the source Vulnerable CVE Program (cve.org) e CISA ADP
Red Hat Red Hat OpenStack Platform 18.0 versions not specified by the source Vulnerable CVE Program (cve.org) e CISA ADP
Pip Keystone < 8.0.0a0 Vulnerable GitHub Security Advisories

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
5.4 CVSS 3.1 Medium 2.8 2.5 secalert@redhat.com via NIST National Vulnerability Database
5.4 CVSS 3.1 Medium — — GitHub, Inc. via GitHub Security Advisories
5.4 CVSS 3.1 Medium — — redhat via CVE Program (cve.org) e CISA ADP
3.5 CVSS 2.0 Low 6.8 2.9 nvd@nist.gov via NIST National Vulnerability Database
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N (score shown at the top: secalert@redhat.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-639 · Authorization Bypass Through User-Controlled Key (IDOR)

Other CVEs with this weakness →

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
  • Audit administrative actions and access to resources outside each user’s normal pattern.
web/proxy/WAF logsnetwork IDS/IPSauthentication logsapplication logs

Timeline

What happened to this CVE, newest first.

  • 2026
  • Fix documented
    Oct 30, 2026 · GitHub Security Advisories
  • Affected products added · pip/keystone
    Oct 30, 2026 · GitHub Security Advisories
  • Affected products added · red hat/openstack essex for rhel 6, red hat/openstack folsom for rhel 6, red hat/red hat openstack platform 13 (queens),
    Oct 30, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 30, 2026
  • Fix documented
    Oct 30, 2026 · NIST National Vulnerability Database
  • Affected products added · openstack/essex, openstack/folsom
    Oct 30, 2026 · NIST National Vulnerability Database
  • CVSS changed · 5.4
    Oct 30, 2026 · NIST National Vulnerability Database
  • Source status changed · → Modified
    Oct 30, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 30, 2026 · Alertas do Telegram
  • 2012
  • CVE published
    Dec 17, 2012 · redhat

Source activity

Repeated readings are counted rather than listed.

  • 2× References added · Oct 30, 2026 – Oct 30, 2026
  • 1× Official description updated · Oct 30, 2026 – Oct 30, 2026

References

20 on the record

Elsewhere on this site

OpenStack
every CVE for this vendor
Access control
same class
CWE-639
other pages naming this weakness

Related CVEs (same products)

  • Medium CVE-2026-93010 Dnsmasq: dnsmasq: --leasequery without address argument applies no source address check 2d
  • Medium CVE-2026-93009 Dnsmasq: dnsmasq: heap out-of-bounds read in dhcpv6 option 39 fqdn decoder 2d
  • Medium CVE-2026-93008 Dnsmasq: dnsmasq: out-of-bailiwick cache injection through cname chase in split-dns configurations 2d
  • Medium CVE-2026-93011 Dnsmasq: dnsmasq: heap out-of-bounds write in dnssec validator via to_wire/from_wire transforms 2d
  • Medium CVE-2026-93006 Dnsmasq: dnsmasq: tftp prefetch cache keyed on stale heap pointer serves wrong file content 2d
  • Medium CVE-2026-93007 Dnsmasq: dnsmasq: tcp/53 child-slot exhaustion starves dnssec validation 2d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No CISA SSVC assessment.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2012-5571 is "Openstack keystone: openstack keystone: authorization bypass via improper ec2 token handling", rated Medium. It affects Essex (OpenStack); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 5.4 describes technical severity. EPSS 2.06% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.