CVE-2014-5251: Medium severity keystone vulnerability

Published Aug 25, 2014
·
Updated

The MySQL token driver in OpenStack Identity (Keystone) 2014.1.x before 2014.1.2.1 and Juno before Juno-3 stores timestamps with the incorrect precision, which causes the expiration comparison for tokens to fail and allows remote authenticated users to retain access via an expired token.

Affected Software

6 affected componentsFixes available
pip/keystone<8.0.0a0
8.0.0a0
Openstack Keystone=2014.1
Openstack Keystone=2014.1.2
Openstack Keystone=juno-1
Openstack Keystone=juno-2
Canonical Ubuntu Linux=14.04

Event History

Aug 25, 2014
CVE Published
via MITRE·02:00 PM
Data Sourced
via MITRE·02:00 PM
Description
May 17, 2022
Advisory Published
via GitHub·04:31 AM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2014-5251?

CVE-2014-5251 is considered a medium severity vulnerability due to its potential for abuse by authenticated users.

2

How do I fix CVE-2014-5251?

To fix CVE-2014-5251, upgrade OpenStack Keystone to version 2014.1.2.1 or newer, or Juno to Juno-3 or later.

3

What is the impact of CVE-2014-5251?

The impact of CVE-2014-5251 allows remote authenticated users to retain access to resources using expired tokens due to incorrect timestamp handling.

4

Which versions of OpenStack Keystone are affected by CVE-2014-5251?

OpenStack Keystone versions 2014.1.x before 2014.1.2.1 and Juno before Juno-3 are affected by CVE-2014-5251.

5

Who can exploit CVE-2014-5251?

CVE-2014-5251 can be exploited by remote authenticated users who have access to tokens in the affected OpenStack Keystone versions.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203