LiveActive security incident?Get immediate response
CVE Record

CVE-2012-3426: OpenStack Keystone before 2012.1.1, as used in OpenStack Folsom before Folsom-1 and OpenStack Essex, does n...

OpenStack Keystone before 2012.1.1, as used in OpenStack Folsom before Folsom-1 and OpenStack Essex, does not properly implement token expiration, which allows remote authenticated users to bypass intended authorization restrictions by (1) creating new tokens through token chaining, (2) leveraging possession of a token for a disabled user account, or (3) leveraging possession of a token for an account with a changed password.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysis

Security readout for executives and security teams

In affected OpenStack Keystone versions, tokens could remain useful when they should expire or be invalidated. A signed-in or token-holding user might keep accessing cloud APIs after a password change or account disablement, or create fresh tokens from existing ones. For old Essex/Folsom Keystone clouds, this weakens identity and offboarding controls. Exposure is limited to environments running historic OpenStack Keystone versions before 2012.1.1 or Folsom-1. Modern OpenStack deployments are unlikely affected unless they use unpatched legacy packages or forks. Public cloud control planes, private clouds, and lab deployments using those Keystone builds are the relevant scope. Prioritize remediation if any legacy Keystone deployment remains in production or connected to sensitive cloud resources. The issue can undermine account disablement and password-change controls, which are core incident-response and employee offboarding safeguards. If no affected Keystone versions exist, residual business risk is low. Mitigation focus: Upgrade Keystone to 2012.1.1 or later vendor-supported packages.; Review OpenStack and distribution advisories for deployment-specific remediation guidance.; Invalidate or rotate existing Keystone tokens after upgrading affected services..

Prepared

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-3426 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
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

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.