OpenStack Identity (Keystone) Trustee token revocations does not work with memcache backend

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

7.1 · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2014-2237: 1.37% estimated exploitation activity in the next 30 days; percentile 71.89 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

The memcache token backend in OpenStack Identity (Keystone) 2013.1 through 2.013.1.4, 2013.2 through 2013.2.2, and icehouse before icehouse-3, when issuing a trust token with impersonation enabled, does not include this token in the trustee's token-index-list, which prevents the token from being invalidated by bulk token revocation and allows the trustee to bypass intended access restrictions.

Published by the source

17 May 2022, 04:13 UTC

Last modified by the source

13 Apr 2025, 23:04 UTC

Source last checked

26 Oct 2026, 13:31 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-23x9-8hxr-978c

2. Revision 2 · amended · 25 Oct 2026

   Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

3. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-23x9-8hxr-978c

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2014-2237

Advisory: OpenStack Identity (Keystone) Trustee token revocations does not work with memcache backend
IDs: CVE-2014-2237, GHSA-23x9-8hxr-978c
Record: https://patchnext.com/advisories/cve-2014-2237 (revision 3, source checked 26 Oct 2026, 13:31 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: keystone 8.0.0a0. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI keystone: affected < 8.0.0a0; fixed in 8.0.0a0

## Suggested inspection (read-only)
- `python -m pip show keystone`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on keystone.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-23x9-8hxr-978c (OSV record GHSA-23x9-8hxr-978c lists affected ranges: PyPI keystone >=0 <8.0.0a0 (fixed))
- Verified: https://github.com/advisories/GHSA-23x9-8hxr-978c (GitHub-reviewed advisory GHSA-23x9-8hxr-978c lists affected ranges: PyPI keystone >=0 <8.0.0a0)

Commands are suggestions: review each one before running it.