python-keystoneclient vulnerable to context confusion in Keystone auth_token middleware
A context confusion vulnerability was identified in Keystone auth_token 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 auth_token with memcache are vulnerable.
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2014-0105US | medium6.0 | — | ||
The auth_token middleware in the OpenStack Python client library for Keystone (aka python-keystoneclient) before 0.7.0 does not properly retrieve user tokens from memcache, which a… | ||||
references
External citations — patches, advisories, analysis.
- http://rhn.redhat.com/errata/RHSA-2014-0382.htmlWEB
- http://rhn.redhat.com/errata/RHSA-2014-0409.htmlWEB
- http://www.openwall.com/lists/oss-security/2014/03/27/4WEB
- https://bugs.launchpad.net/python-keystoneclient/+bug/1282865WEB
- https://github.com/openstack/python-keystoneclientPACKAGE
- https://github.com/pypa/advisory-database/tree/main/vulns/python-keystoneclient/PYSEC-2014-70.yamlWEB
- https://nvd.nist.gov/vuln/detail/CVE-2014-0105ADVISORY
- https://review.opendev.org/c/openstack/python-keystoneclient/+/81078WEB
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan