A context confusion vulnerability was identified in Keystone authtoken middleware (shipped in python-keystoneclient) before 0.7.0. By doing repeated requests, with sufficient load on the target system, an authenticated user may in certain situations assume another authenticated user's complete identity and multi-tenant authorizations, potentially resulting in a privilege escalation. Note that it is related to a bad interaction between eventlet and python-memcached that should be avoided if the calling process already monkey-patches "thread" to use eventlet. Only keystone middleware setups using authtoken with memcache are vulnerable.

python-keystoneclient version 0.2.3 to 0.2.5 has middleware memcache encryption bypass

python-keystoneclient version 0.2.3 to 0.2.5 has middleware memcache signing bypass

A vulnerability was discovered in OpenStack:

Title: S3Token TLS cert verification option not honored Reporter: Brant Knudson (IBM) Products: keystonemiddleware, python-keystoneclient Affects: versions up to 1.5.0 (keystonemiddleware), versions up to 0.11.2 (python-keystoneclient)

Description: Brant Knudson from IBM reported a vulnerability in keystonemiddleware (formerly shipped as python-keystoneclient). When the 'insecure' option is set in a S3Token paste configuration file its value is effectively ignored and instead assumed to be true. As a result certificate verification will be disabled, leaving TLS connections open to MITM attacks. Note that it's unusual to explicitly add this option and then set it to false, so the impact of this bug is thought to be limited. All versions of s3token middleware with TLS settings configured are affected by this flaw.

Acknowledgements:

Red Hat would like to thank the OpenStack project for reporting this issue. Upstream acknowledges Brant Knudson from IBM as the original reporter.