CVE-2014-2237

What it is

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.

At a glance

Exploitability

Can be exploited over the network without logging in. Limited direct impact.

Exploit odds

1.4% chance of exploitation in the next 30 days (EPSS).

Fix

No patch or advisory is linked yet. Look at mitigations or restrict exposure.

Timeline

1. 2014-04-01 06:35 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 00:06 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 1.4% in the next 30 days (EPSS).
• Severity: 5.0 MEDIUM (CVSS).
• Fix: none linked yet, which raises it.

Details

Published

2014-04-01 06:35 UTC

Last modified

2026-06-17 00:06 UTC

Exploit probability

1.4% · EPSS, next 30 days

Weakness

CWE-264

Record status

Modified

Affected

• Openstack Keystone 2013.1
• Openstack Keystone 2013.1.1
• Openstack Keystone 2013.1.2
• Openstack Keystone 2013.1.3
• Openstack Keystone 2013.1.4
• Openstack Keystone 2013.2.2

Attack profile CVSS 2.0 · 5.0

Attack vector

Network

Complexity

Low

Authentication

None

Confidentiality

None

Integrity

Partial

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2014-2237.md and follow it. Check whether this project is affected by CVE-2014-2237. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge