Skip to content
Fencer Intel
medium 6.6

CVE-2022-2447 json

A flaw was found in Keystone.

published 4y ago modified 4mo ago also EUVD-2022-34708

cvss
6.6
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.7%
EPSS 0.7% chance of exploitation in 30 days, percentile 54%
public exploits
0
none known

Summary

A flaw was found in Keystone. There is a time lag (up to one hour in a default configuration) between when security policy says a token should be revoked from when it is actually revoked. This could allow a remote administrator to secretly maintain access for longer than expected.

Patch / fix

  • python-keystonemiddleware Debian 14, Debian 13, Debian 12 10.1.0-4

debian advisories DEBIAN-CVE-2022-2447

  • keystone Ubuntu 22.04 LTS 2:21.0.1-0ubuntu2.1

ubuntu advisories UBUNTU-CVE-2022-2447

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Is CVE-2022-2447 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-2022-2447 updated cvss 6.6

Openstack: Application credential token remains valid longer than expected

  • Red Hat Integration Data Virtualisation Operator openstack Red Hat JBoss Data Grid 7 openstack Red Hat JBoss Fuse 6 openstack Red Hat JBoss Fuse Service Works 6 openstack Red Hat OpenStack Platform 13 (Queens) python-keystone, openstack-keystone
    affected: no fix planned “Out of support scope”
  • Red Hat OpenStack Platform 16.1 python3-keystone, openstack-keystone
    affected: no fix available
  • Red Hat OpenStack Platform 16.2 python3-keystone, openstack-keystone
    affected: no fix planned “Will not fix”
  • Red Hat OpenStack Platform 17.0 python3-keystone, openstack-keystone
    affected: no fix planned “Out of support scope”
  • Red Hat Quay 3 quay/quay-rhel8 Red Hat Storage 3 python-keystoneclient, python-keystonemiddleware
    affected: no fix planned “Will not fix”
  • Red Hat Enterprise Linux 9 fence-virt, fence-virtd, fence-agents, fence-virtd-cpg, fence-virtd-tcp, fence-agents-all, +51 more Red Hat Integration Camel K 1 openstack Red Hat JBoss Enterprise Application Platform 7 openstack Red Hat JBoss Enterprise Application Platform Expansion Pack openstack
    not affected: vulnerable code not present

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

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

Exploits and checks

  • bugzilla.redhat.com https://bugzilla.redhat.com/show_bug.cgi?id=2105419 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 6.6 CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H

Affected products

  • n/a openstack-keystone

Classification

Weakness
  • CWE-324 Use of a Key Past its Expiration Date
  • CWE-672 Operation on a Resource after Expiration or Release

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.