FedoraOperating system · Fedoraproject
CVE-2013-4222
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedOpenStack Identity (Keystone) Folsom, Grizzly 2013.1.3 and earlier, and Havana before havana-3 does not properly revoke user tokens when a tenant is disabled, which allows remote authenticated users to retain access via the token.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceOpenStack Keystone fails to revoke existing user tokens when a tenant is disabled. When an administrator disables a tenant/project, previously issued tokens remain valid, allowing authenticated users to continue accessing resources under that tenant despite the disabled status.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
FedoraOperating system
= 20
Ubuntu LinuxOperating system
= 12.10= 13.04
OpenstackApplication
= 3.0>= 2013.1, <= 2013.1.3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Authentication
- Single
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:S/C:P/I:P/A:P
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Keystone versionRun keystone --version or check the package manager (rpm -q openstack-keystone or dpkg -l python-keystone)Affected if The installed version is between 2013.1 and 2013.1.3 inclusive
-
Confirm OpenStack deploymentCheck if this is a Keystone identity deployment by reviewing /etc/keystone/keystone.conf or querying keystone endpointAffected if Keystone is deployed as the identity service
-
Verify tenant/project disable feature is in useList tenants/projects (keystone tenant-list) and check for any that have status=disabled or check administrative workflows that involve disabling tenantsAffected if Tenants/projects are being disabled while active tokens exist
-
Check for active tokens from disabled tenantsQuery the token validation endpoint or token database for tokens associated with disabled tenants (keystone token-get for known tokens, or check token backend)Affected if Active tokens exist for tenants marked as disabled
-
Confirm token expiration settingsInspect /etc/keystone/keystone.conf for token expiration settings (default is 24 hours)Affected if Token expiration is set to a long duration, allowing extended access after tenant disable
-
Cross-reference OS/package versionCheck if running Fedora 20, Ubuntu 12.10, Ubuntu 13.04, or Red Hat OpenStack 3.0 which ship with affected Keystone versionsAffected if The underlying OS or OpenStack platform ships with vulnerable Keystone version 2013.1-2013.1.3
You are affected if Keystone version 2013.1 through 2013.1.3 is running and tenants/projects are being disabled while valid tokens for those tenants still exist in the system.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade Keystone to Grizzly 2013.1.4, Havana havana-3, or later which properly invalidate tokens on tenant disable. Alternatively, implement manual token revocation or use shorter token expiration times to limit exposure.
Fix this in Fedora
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-4222 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2013-4222 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data