OpenStack Keystone Grizzly before 2013.1, Folsom, and possibly earlier allows remote attackers to cause a denial of service (CPU and memory consumption) via a large HTTP request, as demonstrated by a long tenant_name when requesting a token.
The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary. This may result in read or write operations on unexpected memory locations that could be linked to other variables, data structures, or internal program data.
Link | Tags |
---|---|
https://launchpad.net/keystone/grizzly/2013.1 | third party advisory patch |
https://github.com/openstack/keystone/commit/82c87e5638ebaf9f166a9b07a0155291276d6fdc | third party advisory |
https://bugzilla.redhat.com/show_bug.cgi?id=909012 | third party advisory |
https://github.com/openstack/keystone/commit/7691276b869a86c2b75631d5bede9f61e030d9d8 | third party advisory |
https://bugs.launchpad.net/keystone/+bug/1099025 | third party advisory |
http://rhn.redhat.com/errata/RHSA-2013-0708.html | third party advisory vendor advisory |