Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
First Last Prev Next    This bug is not in your last search results.
Bug 1127250 - (CVE-2014-5252) CVE-2014-5252 openstack-keystone: token expiration date stored incorrectly
CVE-2014-5252 openstack-keystone: token expiration date stored incorrectly
Status: CLOSED ERRATA
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
low Severity low
: ---
: ---
Assigned To: Red Hat Product Security
impact=low,public=20140725,reported=2...
: Security
Depends On: 1131344 1131345
Blocks: 1127260
  Show dependency tree / graph
 
Reported: 2014-08-06 09:05 EDT by Vasyl Kaigorodov
Modified: 2016-04-26 15:10 EDT (History)
23 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
A flaw was found in keystone revocation events that resulted in the "issued_at" time being updated when a token created by the V2 API was processed by the V3 API. This could allow a user to evade token revocation. Only OpenStack Identity setups configured to make use of revocation events and UUID tokens were affected.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2014-09-02 15:46:52 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2014:1121 normal SHIPPED_LIVE Low: openstack-keystone security and bug fix update 2014-09-02 17:58:31 EDT
Red Hat Product Errata RHSA-2014:1122 normal SHIPPED_LIVE Low: openstack-keystone security and bug fix update 2014-09-02 17:58:25 EDT

  None (edit)
Description Vasyl Kaigorodov 2014-08-06 09:05:04 EDT 
It was reported [1] that in Keystone V2 token support, by creating a token using the V2 API, a user may evade token revocation.
When the token is processed by the V3 API, its "issued_at" time is wrongly updated and then the service will fail to revoke it.
Only Keystone setups configured to use revocation events and UUID tokens are affected.

CVE request has been sent to oss-security mailing list by upstream [2]

Commit that fixes this issue:
https://git.openstack.org/cgit/openstack/keystone/commit/?id=a4c73e4382cb062aa9f30fe1960d5014d3c49cc2

[1]: https://bugs.launchpad.net/keystone/+bug/1348820
[2]: http://seclists.org/oss-sec/2014/q3/296
Comment 2 Vasyl Kaigorodov 2014-08-06 10:17:40 EDT 
It's stated in the Launchpad ticket that this would only impact Icehouse (openstack-2014.X) since that's where revocation events were added.
Comment 3 Garth Mollett 2014-08-15 01:35:45 EDT 
Statement:

This issue does not affected openstack-keystone as shipped with Red Hat Enterprise Linux OpenStack Platform 4.0.
Comment 4 Garth Mollett 2014-08-15 01:39:40 EDT 
Keystone in RHEL-OSP-5 (Icehouse) includes this code, although it is marked as experimental in Icehouse upstream, we do include an example of how to enable it in our documentation and thus will need to release an erratum.
Comment 6 Martin Prpič 2014-08-25 04:44:37 EDT 
IssueDescription:

A flaw was found in keystone revocation events that resulted in the "issued_at" time being updated when a token created by the V2 API was processed by the V3 API. This could allow a user to evade token revocation. Only OpenStack Identity setups configured to make use of revocation events and UUID tokens were affected.
Comment 8 errata-xmlrpc 2014-09-02 13:58:52 EDT 
This issue has been addressed in following products:

  OpenStack 5 for RHEL 6

Via RHSA-2014:1122 https://rhn.redhat.com/errata/RHSA-2014-1122.html
Comment 9 errata-xmlrpc 2014-09-02 13:59:14 EDT 
This issue has been addressed in following products:

  OpenStack 5 for RHEL 7

Via RHSA-2014:1121 https://rhn.redhat.com/errata/RHSA-2014-1121.html
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.