Bug 957028 (CVE-2013-2014) - CVE-2013-2014 OpenStack keystone: no limitation for requests and headers size which can cause a crash
Summary: CVE-2013-2014 OpenStack keystone: no limitation for requests and headers size...
Keywords:
Status: CLOSED ERRATA
Alias: CVE-2013-2014
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 957029 957030 957031
Blocks: 957039
TreeView+ depends on / blocked
 
Reported: 2013-04-26 08:18 UTC by Kurt Seifried
Modified: 2019-09-29 13:03 UTC (History)
19 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-08-09 03:24:54 UTC
Embargoed:


Attachments (Terms of Use)

Description Kurt Seifried 2013-04-26 08:18:27 UTC
Yaguang Tang reports:

concurrent requests with large POST body can crash the keystone process.

this can be used by Malicious and lead to DOS to Cloud Service Provider.

The OpenStack project has confirmed:

Concurrent Keystone POST requests with large body messages are held in memory 
without filtering or rate limiting, this can lead to resource exhaustion on 
the Keystone server.

External references:
https://bugs.launchpad.net/keystone/+bug/1098177
https://bugs.launchpad.net/ossn/+bug/1155566

Comment 1 Kurt Seifried 2013-04-26 08:19:21 UTC
Created openstack-keystone tracking bugs for this issue

Affects: fedora-all [bug 957029]

Comment 2 Kurt Seifried 2013-04-26 08:20:13 UTC
Created openstack-keystone tracking bugs for this issue

Affects: epel-6 [bug 957030]

Comment 4 Kurt Seifried 2013-05-25 07:46:31 UTC
This has been fixed upstream in OpenStack Grizzly https://review.openstack.org/#/c/19567/

Comment 5 Fedora Update System 2013-07-20 09:32:14 UTC
openstack-keystone-2013.1.2-3.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.


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