# CVE-2022-2447: Security feature bypass in openstack-keystone

> A time lag in token revocation allows remote administrators to maintain unauthorized access longer than intended in OpenStack Keystone.

- **Severity:** Medium 6.6 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 1 Sep 2022
- **Updated:** 3 Aug 2024
- **Also known as:** DEBIAN-CVE-2022-2447, GHSA-r88f-774m-5rj4, UBUNTU-CVE-2022-2447

## What is CVE-2022-2447?

CVE-2022-2447 is a medium-severity vulnerability in openstack-keystone, published on 1 Sep 2022. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

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.

Weakness: CWE-672 (Operation on a Resource after Expiration or Release), CWE-324 (Use of a Key Past its Expiration Date)

## Which versions are affected by CVE-2022-2447?

It affects 4 products.


Products: Openstack Keystone, Redhat Openstack Platform, Redhat Quay, Redhat Storage.

## How do I fix CVE-2022-2447?

Apply the vendor's patch.

## Is CVE-2022-2447 being exploited?

There is no known exploitation of CVE-2022-2447 in the wild and no public exploit code.

## Other vulnerabilities in openstack-keystone

- [CVE-2020-12690](https://insights.sbomify.com/CVE-2020-12690/): Insufficient Session Expiration in OpenStack Keystone (high 8.8)
- [CVE-2019-19687](https://insights.sbomify.com/CVE-2019-19687/): OpenStack Keystone Credential Leakage (high 8.8)
- [CVE-2026-43001](https://insights.sbomify.com/CVE-2026-43001/): OpenStack Keystone has an Incorrect Authorization Issue (high 7.9)
- [CVE-2014-2828](https://insights.sbomify.com/CVE-2014-2828/): OpenStack Identity (Keystone) DoS through V3 API authentication chaining (high 7.8)
- [CVE-2021-38155](https://insights.sbomify.com/CVE-2021-38155/): OpenStack Keystone allows information disclosure during account locking (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-2447 and fix it if it is affected.

What it is: CVE-2022-2447 is a medium-severity vulnerability in openstack-keystone, published on 1 Sep 2022. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-2447 in the wild and no public exploit code.

Affected product: openstack-keystone. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-2447/ (Markdown: https://insights.sbomify.com/CVE-2022-2447/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-2447
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-2447
- OSV: https://osv.dev/vulnerability/CVE-2022-2447

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-2447/
Summaries are generated and may contain mistakes; the official description above is the record.