Bug 995598 (CVE-2013-4222) - CVE-2013-4222 OpenStack: Keystone disabling a tenant does not disable a user token
Summary: CVE-2013-4222 OpenStack: Keystone disabling a tenant does not disable a user ...
Alias: CVE-2013-4222
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
Depends On: 995601 995602 995603 995604 995605
Blocks: 995600
TreeView+ depends on / blocked
Reported: 2013-08-09 19:59 UTC by Kurt Seifried
Modified: 2019-09-29 13:07 UTC (History)
24 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2013-11-18 21:34:00 UTC

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2013:1524 0 normal SHIPPED_LIVE Moderate: openstack-keystone security and bug fix update 2013-11-19 00:23:46 UTC

Description Kurt Seifried 2013-08-09 19:59:48 UTC
### Summary ###
When a tenant is disabled in Keystone, tokens that have been issued to
that tenant are not invalidated. This can result in users having access
to your cloud after you have attempted to revoke them.

### Affected Services / Software ###

### Discussion ###
It appears that Keystone does not purge the tokens given out to tenants
when a tenant is disabled. In some scenarios this could be very
important to cloud providers. Take the case where a cloud provider must
a tenant's access because of some legal investigation. Even though the
tenant is disabled it would be possible for them to terminate VMs /
delete Swift files etc. - There are many other abuse-cases...

### Recommended Actions ###
How the tokens are stored depends on your cloud deployment. If you
deploy using Memcache to back Keystone then flushing the cash when
disabling a token would resolve this issue for you, at the cost of other
token lookups which are no longer in the cash requiring Keystone

It is of course possible to script something to remove tokens from any
backend DB or cache but there is no 'official' way to do this.

### Contacts / References ###
Proposed Fix : https://review.openstack.org/#/c/39878/
This OSSN : https://bugs.launchpad.net/ossn/+bug/1179955
OpenStack Security ML : openstack-security at lists.openstack.org
OpenStack Security Group : https://launchpad.net/~openstack-ossg


Comment 2 Kurt Seifried 2013-08-09 20:06:12 UTC
Created openstack-keystone tracking bugs for this issue:

Affects: fedora-all [bug 995601]
Affects: epel-6 [bug 995602]

Comment 3 Fedora Update System 2013-09-23 00:28:52 UTC
openstack-keystone-2013.2-0.9.b3.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 4 errata-xmlrpc 2013-11-18 19:29:46 UTC
This issue has been addressed in following products:

  OpenStack 3 for RHEL 6

Via RHSA-2013:1524 https://rhn.redhat.com/errata/RHSA-2013-1524.html

Note You need to log in before you can comment on or make changes to this bug.