CVE-2014-2237

UnknownEPSS 1.37%

Last modified

CVE-2014-2237 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 1.37% chance of exploitation in the next 30 days.

Description

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.

Metrics

EPSS Probability
1.37%

68.3th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersions
OpenstackKeystone2013.1
OpenstackKeystone2013.1.1
OpenstackKeystone2013.1.2
OpenstackKeystone2013.1.3
OpenstackKeystone2013.1.4
OpenstackKeystone2013.2.2

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2014-2237?
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.
How severe is CVE-2014-2237?
Severity scoring for CVE-2014-2237 is pending analysis. The EPSS model estimates a 1.37% probability of exploitation in the next 30 days.
How do I fix CVE-2014-2237?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2014-2237?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST