Bug 960203 (CVE-2013-2059)

Summary: CVE-2013-2059 OpenStack Keystone: tokens not immediately invalidated when user is deleted
Product: [Other] Security Response Reporter: Kurt Seifried <kseifried>
Component: vulnerabilityAssignee: Red Hat Product Security <security-response-team>
Status: CLOSED ERRATA QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: abaron, aortega, apevec, ayoung, chrisw, cpelland, dallan, gkotton, jlieskov, jrusnack, markmc, rbryant, security-response-team, ykaul
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-05-25 07:59:19 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 960207, 961858, 961859    
Bug Blocks: 960205    
Attachments:
Description Flags
folsom-CVE-2013-2059.patch
none
grizzly-CVE-2013-2059.patch
none
havana-CVE-2013-2059.patch none

Description Kurt Seifried 2013-05-06 16:57:58 UTC 
Thierry Carrez reports:

Title: Keystone tokens not immediately invalidated when user is deleted
Reporter: Sam Stoelinga
Products: Keystone
Affects: Folsom, Grizzly

Description:
Sam Stoelinga reported a vulnerability in Keystone. When users are
deleted through Keystone v2 API, existing tokens for those users are not
immediately invalidated and remain valid for the duration of the token's
life (by default, up to 24 hours). This may result in users retaining
access when the administrator of the system thought them disabled. You
can workaround this issue by disabling a user before deleting it: in
that case the tokens belonging to the disabled user are immediately
invalidated. Keystone setups using the v3 API call to delete users are
unaffected.
Comment 2 Kurt Seifried 2013-05-06 17:08:49 UTC 
Created attachment 744263 [details]
folsom-CVE-2013-2059.patch
Comment 3 Kurt Seifried 2013-05-06 17:09:20 UTC 
Created attachment 744264 [details]
grizzly-CVE-2013-2059.patch
Comment 4 Kurt Seifried 2013-05-06 17:09:38 UTC 
Created attachment 744265 [details]
havana-CVE-2013-2059.patch
Comment 5 Jan Lieskovsky 2013-05-10 15:08:49 UTC 
References:
  http://www.openwall.com/lists/oss-security/2013/05/09/3
  https://bugs.launchpad.net/keystone/+bug/1166670

Upstream patches:
  https://review.openstack.org/#/c/28677/ (Havana branch)
  https://review.openstack.org/#/c/28678/ (Grizzly branch)
  https://review.openstack.org/#/c/28679/ (Folsom branch)
Comment 6 Jan Lieskovsky 2013-05-10 15:11:10 UTC 
Created openstack-keystone tracking bugs for this issue

Affects: fedora-all [bug 961858]
Affects: epel-6 [bug 961859]
Comment 7 Fedora Update System 2013-05-22 01:29:13 UTC 
openstack-keystone-2012.2.4-3.fc18 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.
Comment 8 Fedora Update System 2013-05-24 20:25:50 UTC 
openstack-keystone-2013.1.1-1.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.