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 1127253 - (CVE-2014-5253) CVE-2014-5253 openstack-keystone: domain-scoped tokens don't get revoked
CVE-2014-5253 openstack-keystone: domain-scoped tokens don't get revoked
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=20140728,reported=2...
: Security
Depends On: 1131344 1131345
Blocks: 1127260
  Show dependency tree / graph
 
Reported: 2014-08-06 09:11 EDT by Vasyl Kaigorodov
Modified: 2016-04-26 11:32 EDT (History)
23 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
It was discovered that domain-scoped tokens were not revoked when a domain was disabled. Only OpenStack Identity setups configured to make use of revocation events were affected.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2014-09-02 15:47:01 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:11:28 EDT 
It was reported [1] that if a domain is invalidated (which generates a revocation event),
that revocation event won't match domain-scoped tokens so those tokens won't be revoked.

This is because the code to calculate the fields for a domain-scoped token don't use the
domain-scope so that information can't be used when testing against the revocation events.

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

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

[1]: https://bugs.launchpad.net/keystone/+bug/1349597
[2]: http://seclists.org/oss-sec/2014/q3/296
Comment 2 Vasyl Kaigorodov 2014-08-06 10:17:51 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:57 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:49 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:56 EDT 
IssueDescription:

It was discovered that domain-scoped tokens were not revoked when a domain was disabled. Only OpenStack Identity setups configured to make use of revocation events were affected.
Comment 8 errata-xmlrpc 2014-09-02 13:58:56 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:18 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.