| CVE-2014-0105 |
medium |
— |
6.0 |
|
|
|
12y ago |
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 allows remote authen… |
| CVE-2013-2104 |
medium |
— |
5.5 |
|
|
|
4y ago |
python-keystoneclient before 0.2.4, as used in OpenStack Keystone (Folsom), does not properly check expiry for PKI tokens, which allows remote authenticated users to (1) retain use of a token after i… |
| CVE-2014-7144 |
medium |
— |
4.3 |
|
|
|
4y ago |
OpenStack keystonemiddleware (formerly python-keystoneclient) 0.x before 0.11.0 and 1.x before 1.2.0 disables certification verification when the "insecure" option is set in a paste configuration (pa… |
| CVE-2015-1852 |
medium |
— |
4.3 |
|
|
|
11y ago |
The s3_token middleware in OpenStack keystonemiddleware before 1.6.0 and python-keystoneclient before 1.4.0 disables certification verification when the "insecure" option is set in a paste configurat… |
| CVE-2013-2030 |
low |
— |
2.1 |
|
|
|
13y ago |
keystone/middleware/auth_token.py in OpenStack Nova Folsom, Grizzly, and Havana uses an insecure temporary directory for storing signing certificates, which allows local users to spoof servers by pre… |
| CVE-2013-2013 |
low |
— |
2.1 |
|
|
|
13y ago |
The user-password-update command in python-keystoneclient before 0.2.4 accepts the new password in the --password argument, which allows local users to obtain sensitive information by listing the pro… |
| CVE-2013-2255 |
unknown |
— |
— |
|
|
|
4y ago |
HTTPSConnections in OpenStack Keystone 2013, OpenStack Compute 2013.1, and possibly other OpenStack components, fail to validate server-side SSL certificates. |
| CVE-2013-2166 |
unknown |
— |
— |
|
|
|
5y ago |
python-keystoneclient version 0.2.3 to 0.2.5 has middleware memcache encryption bypass |
| CVE-2013-2167 |
unknown |
— |
— |
|
|
|
6y ago |
python-keystoneclient version 0.2.3 to 0.2.5 has middleware memcache signing bypass |
