CVE-2012-5563: n/a vulnerability

CVE-2012-5563: OpenStack Keystone, as used in OpenStack Folsom 2012.2, does not properly implement token expiration, which...

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.

UnknownCVSS not scoredNot KEV-listedUpdatedAug 6, 2024, 21:14 UTC (UTC+00:00)

Security readout for executives and security teams

Keystone could let an already authenticated OpenStack user keep access longer than intended by obtaining new tokens from existing ones. This weakens session expiration and authorization boundaries in OpenStack Folsom 2012.2 environments using affected Keystone code. Exposure is most likely in legacy OpenStack Folsom 2012.2 deployments or downstream packages referenced by Red Hat and Ubuntu advisories. Modern OpenStack environments are only relevant if they carry the affected Keystone regression. Treat as a legacy cloud-control-plane issue. Prioritize if the organization still operates OpenStack Folsom-era Keystone or inherited old appliances. Otherwise, document non-exposure and monitor only for legacy remnants. Mitigation focus: Identify any OpenStack Keystone Folsom 2012.2 or matching downstream packages.; Review RHSA-2012:1557 and USN-1641-1 for applicable vendor updates.; Apply vendor-supported Keystone fixes or upgrade affected OpenStack components..

Prepared: Jun 24, 2026, 12:04 UTC (UTC+00:00)

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup

cve · low confidence lookup

CVE-2012-5563 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup

Vulnerability profileCVE Program record

Severity: Unknown
CVSS: Not scored
Known Exploited: No
Published: Dec 18, 2012, 01:00 UTC (UTC+00:00)

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors

0Timeline events

0ADP providers

5Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

CVE List V5 sourceCVE List V5
https://github.com/openstack/keystone/commit/38c7e46a640a94da4da89a39a5a1ea9c081f1eb5CVE reference · x_refsource_CONFIRM
https://github.com/openstack/keystone/commit/f9d4766249a72d8f88d75dcf1575b28dd3496681CVE reference · x_refsource_CONFIRM
https://bugs.launchpad.net/keystone/+bug/1079216CVE reference · x_refsource_CONFIRM
folsom-tokens-security-bypass(80370)CVE reference · vdb-entry, x_refsource_XF

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus

n/an/an/aListed

Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.