CVE-2015-1852 – keystonemiddleware/keystoneclient: S3Token TLS cert verification option not honored
https://notcve.org/view.php?id=CVE-2015-1852
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 configuration (paste.ini) file regardless of the value, which allows remote attackers to conduct man-in-the-middle attacks via a crafted certificate, a different vulnerability than CVE-2014-7144. El middleware s3_token en OpenStack keystonemiddleware anterior a 1.6.0 y python-keystoneclient anterior a 1.4.0 deshabilita la verificación de certificados cuando la opción 'inseguro' esté configurada en un fichero de configuración paste (paste.ini) independientemente de su valor, lo que permite a atacantes remotos realizar ataques man-in-the-middle a través de un certificado manipulado, una vulnerabilidad diferente a CVE-2014-7144. It was discovered that some items in the S3Token paste configuration as used by python-keystonemiddleware (formerly python-keystoneclient) were incorrectly evaluated as strings, an issue similar to CVE-2014-7144. If the "insecure" option were set to "false", the option would be evaluated as true, resulting in TLS connections being vulnerable to man-in-the-middle attacks. Note: the "insecure" option defaults to false, so setups that do not specifically define "insecure=false" are not affected. • http://lists.openstack.org/pipermail/openstack-announce/2015-April/000350.html http://rhn.redhat.com/errata/RHSA-2015-1677.html http://rhn.redhat.com/errata/RHSA-2015-1685.html http://www.oracle.com/technetwork/topics/security/bulletinapr2015-2511959.html http://www.securityfocus.com/bid/74187 http://www.ubuntu.com/usn/USN-2705-1 https://bugs.launchpad.net/keystonemiddleware/+bug/1411063 https://access.redhat.com/security/cve/CVE-2015-1852 https://bugzilla.redhat.com/show_bug.cg • CWE-17: DEPRECATED: Code CWE-295: Improper Certificate Validation •
CVE-2014-7144 – python-keystoneclient: TLS certificate verification disabled
https://notcve.org/view.php?id=CVE-2014-7144
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 (paste.ini) file regardless of the value, which allows remote attackers to conduct man-in-the-middle attacks via a crafted certificate. OpenStack keystonemiddleware (anteriormente python-keystoneclient) 0.x anterior a 0.11.0 y 1.x anterior a 1.2.0 deshabilita la verificación de certificados cuando la opción 'inseguro' está configurada en un fichero de la configuración del pegar (paste.ini) independientemente del valor, lo que permite a atacantes remotos realizar ataques de man-in-the-middle a través de un certificado manipulado. It was found that python-keystoneclient treated all settings in paste.ini files as string types. If the "insecure" option were set to any value in a paste.ini configuration file, it would be evaluated as true, resulting in TLS connections being vulnerable to man-in-the-middle attacks. • http://rhn.redhat.com/errata/RHSA-2014-1783.html http://rhn.redhat.com/errata/RHSA-2014-1784.html http://rhn.redhat.com/errata/RHSA-2015-0020.html http://secunia.com/advisories/62709 http://www.openwall.com/lists/oss-security/2014/09/25/51 http://www.securityfocus.com/bid/69864 http://www.ubuntu.com/usn/USN-2705-1 https://bugs.launchpad.net/python-keystoneclient/+bug/1353315 https://access.redhat.com/security/cve/CVE-2014-7144 https://bugzilla.redhat.com/ • CWE-295: Improper Certificate Validation CWE-310: Cryptographic Issues •
CVE-2014-0105 – python-keystoneclient: Potential context confusion in Keystone middleware
https://notcve.org/view.php?id=CVE-2014-0105
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 authenticated users to gain privileges in opportunistic circumstances via a large number of requests, related to an "interaction between eventlet and python-memcached." El middleware auth_token en la librería del cliente Python de OpenStack para Keystone (también conocido como python-keystoneclient) anterior a 0.7.0 no consigue debidamente tokens de usuario de la memcache, lo cual permite a usuarios remotos autenticados ganar privilegios en circunstancias oportunistas a través de un gran número de peticiones, relacionado con una "interacción entre eventlet y python-memcached.". • http://rhn.redhat.com/errata/RHSA-2014-0382.html http://rhn.redhat.com/errata/RHSA-2014-0409.html http://www.openwall.com/lists/oss-security/2014/03/27/4 https://bugs.launchpad.net/python-keystoneclient/+bug/1282865 https://access.redhat.com/security/cve/CVE-2014-0105 https://bugzilla.redhat.com/show_bug.cgi?id=1082165 • CWE-255: Credentials Management Errors •
CVE-2013-2013
https://notcve.org/view.php?id=CVE-2013-2013
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 process. El comando user-password-update en python-keystoneclient anteriores a 0.2.4 acepta la nueva contraseña en el argumento --password, lo que permite a usuarios locales obtener información sensible listando el proceso. • http://www.openwall.com/lists/oss-security/2013/05/23/4 https://bugs.launchpad.net/python-keystoneclient/+bug/938315 https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A16937 • CWE-200: Exposure of Sensitive Information to an Unauthorized Actor •
CVE-2013-2104 – Keystone: Missing expiration check in Keystone PKI token validation
https://notcve.org/view.php?id=CVE-2013-2104
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 it has expired, or (2) use a revoked token once it expires. python-keystoneclient anterior a la versión 0.2.4, tal como se usa en OpenStack Keystone (Folsom), no comprueba adecuadamente la expiración de tokens PKI, lo que permite a usuarios autenticados (1) conservar la utilización de un token después de su expiración, o (2) usar un token revocado una vez expira. • http://lists.opensuse.org/opensuse-updates/2013-06/msg00198.html http://rhn.redhat.com/errata/RHSA-2013-0944.html http://www.openwall.com/lists/oss-security/2013/05/28/7 http://www.ubuntu.com/usn/USN-1851-1 http://www.ubuntu.com/usn/USN-1875-1 https://bugs.launchpad.net/python-keystoneclient/+bug/1179615 https://access.redhat.com/security/cve/CVE-2013-2104 https://bugzilla.redhat.com/show_bug.cgi?id=965852 • CWE-264: Permissions, Privileges, and Access Controls CWE-613: Insufficient Session Expiration •