First published: Mon 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.
Credit: cve@mitre.org cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
pip/keystone | <8.0.0a0 | 8.0.0a0 |
OpenStack keystonemiddleware | =2014.1 | |
OpenStack keystonemiddleware | =2014.1.2 | |
OpenStack keystonemiddleware | =juno-1 | |
OpenStack keystonemiddleware | =juno-2 | |
Ubuntu Linux | =14.04 | |
Ubuntu | =14.04 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2014-5251 is considered a medium severity vulnerability due to its potential for abuse by authenticated users.
To fix CVE-2014-5251, upgrade OpenStack Keystone to version 2014.1.2.1 or newer, or Juno to Juno-3 or later.
The impact of CVE-2014-5251 allows remote authenticated users to retain access to resources using expired tokens due to incorrect timestamp handling.
OpenStack Keystone versions 2014.1.x before 2014.1.2.1 and Juno before Juno-3 are affected by CVE-2014-5251.
CVE-2014-5251 can be exploited by remote authenticated users who have access to tokens in the affected OpenStack Keystone versions.