Skip to content
Noroxi
CVE-2012-5563· NVD / CVE Program· CNA redhat

OpenStack Keystone, as used in OpenStack Folsom 2012.2, does not properly implement token expiration, which allows remote authenticated user

OpenStack Keystone, as used in OpenStack Folsom 2012.2, does not properly implement token expiration, which allows remote authenticated users to bypass intended authorization restrictions by creating new tokens through token chaining. NOTE: this issue exists because of a CVE-2012-3426 regression.

MediumCVSS 4.0 · v2.0—No exploit Fix available
Published
Dec 17, 2012
Updated
Jun 16, 2026
EPSS
2.9% · 86th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

17

Monitor

Low priority for now.

CVSS
16 / 40 · 4.0 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 2.9%

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Affected systems

VendorProduct
openstackfolsom

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • openstack folsom2012.2

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
PyPIkeystonebefore 8.0.08.0.0
PyPIkeystoneall versions—
Red Hat:openstack:2::el6openstack-keystonebefore 0:2012.2.1-1.el6ost0:2012.2.1-1.el6ost
Red Hat:openstack:2::el6openstack-keystone-docbefore 0:2012.2.1-1.el6ost0:2012.2.1-1.el6ost
Red Hat:openstack:2::el6python-keystonebefore 0:2012.2.1-1.el6ost0:2012.2.1-1.el6ost

Other highest-scoring records for the same primary product.

  • CVE-2013-2161XML injection vulnerability in account/utils.py in OpenStack Swift Folsom, Grizzly, and Havana allows attackers to trigger invalid or spoofe
    31Monitor
  • CVE-2013-1865OpenStack Keystone Folsom (2012.2) does not properly perform revocation checks for Keystone PKI tokens when done through a server, which all
    28Monitor
  • CVE-2013-1665The XML libraries for Python 3.4, 3.3, 3.2, 3.1, 2.7, and 2.6, as used in OpenStack Keystone Essex and Folsom, Django, and possibly other pr
    21Monitor
  • CVE-2012-3447virt/disk/api.py in OpenStack Compute (Nova) 2012.1.x before 2012.1.2 and Folsom before Folsom-3 allows remote authenticated users to overwr
    20Monitor
  • CVE-2012-5625OpenStack Compute (Nova) Folsom before 2012.2.2 and Grizzly, when using libvirt and LVM backed instances, does not properly clear physical v
    18Monitor
  • CVE-2013-4155OpenStack Swift before 1.9.1 in Folsom, Grizzly, and Havana allows authenticated users to cause a denial of service ("superfluous" tombstone
    17Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
PyPI:keystone8.0.0Package registry (OSV)
red hat:openstack-keystone0:2012.2.1-1.el6ost · Red Hat:openstack:2::el6Package registry (OSV)
red hat:openstack-keystone-doc0:2012.2.1-1.el6ost · Red Hat:openstack:2::el6Package registry (OSV)
red hat:python-keystone0:2012.2.1-1.el6ost · Red Hat:openstack:2::el6Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
P · data or configuration can be modified
Availability
none
Attack complexity
Low
Confidentiality impact
None
Integrity impact
P
Availability impact
None

CVSS vector

AV:N/AC:L/Au:S/C:N/I:P/A:N

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records