Skip to content
Fencer Intel
medium 6.5

CVE-2013-4222 json

OpenStack Identity (Keystone) Folsom, Grizzly 2013.1.3 and earlier, and Havana before havana-3 does not properly revoke user tokens when a…

published 13y ago modified 4mo ago also EUVD-2013-4126

cvss
6.5
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.9%
EPSS 1.9% chance of exploitation in 30 days, percentile 79%
public exploits
0
none known

Summary

OpenStack 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.

Patch / fix

  • keystone Debian 14, Debian 13, Debian 12 2013.1.3-1

debian advisories DEBIAN-CVE-2013-4222

  • openstack-keystone openstack 3 2013.1.4-1.el6ost
  • python-keystone openstack 3 2013.1.4-1.el6ost

red hat advisories RHSA-2013:1524

Is CVE-2013-4222 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2013-4222 updated cvss 4.0

OpenStack: Keystone disabling a tenant does not disable a user token

  • Red Hat OpenStack Platform 4 openstack-keystone
    affected: no fix available
  • Red Hat Enterprise Linux OpenStack Platform 3.0 python-keystone 2013.1.4-1.el6ost, openstack-keystone 2013.1.4-1.el6ost
    fixed: vendor fix RHSA-2013:1524

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.89% chance of exploitation in the next 30 days, higher than 79% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 6.5 AV:N/AC:L/Au:S/C:P/I:P/A:P

Classification

Weakness
  • CWE-522 Insufficiently Protected Credentials

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.