CVE-2016-4467
https://notcve.org/view.php?id=CVE-2016-4467
The C client and C-based client bindings in the Apache Qpid Proton library before 0.13.1 on Windows do not properly verify that the server hostname matches a domain name in the subject's Common Name (CN) or subjectAltName field of the X.509 certificate when using the SChannel-based security layer, which allows man-in-the-middle attackers to spoof servers via an arbitrary valid certificate. El cliente en C y basado en C, en la librería Apache Qpid Proton anterior a la versión 0.13.1 en Windows no verifica correctamente que el nombre de host del servidor coincide con un nombre de dominio en el Common Name (CN) del asunto o en el campo subjectAltName del certificado X.509 cuando se utiliza una capa de seguridad basada en SChannel, lo que permite a atacantes miTm suplantar servidores a través de un certificado válido. • http://www.openwall.com/lists/oss-security/2016/07/15/3 http://www.securityfocus.com/bid/91788 http://www.securitytracker.com/id/1036316 https://lists.apache.org/thread.html/914424e4d798a340f523b6169aaf39b626971d9bb00fcdeb1d5d6c0d%40%3Ccommits.qpid.apache.org%3E • CWE-295: Improper Certificate Validation •
CVE-2016-8741
https://notcve.org/view.php?id=CVE-2016-8741
The Apache Qpid Broker for Java can be configured to use different so called AuthenticationProviders to handle user authentication. Among the choices are the SCRAM-SHA-1 and SCRAM-SHA-256 AuthenticationProvider types. It was discovered that these AuthenticationProviders in Apache Qpid Broker for Java 6.0.x before 6.0.6 and 6.1.x before 6.1.1 prematurely terminate the SCRAM SASL negotiation if the provided user name does not exist thus allowing remote attacker to determine the existence of user accounts. The Vulnerability does not apply to AuthenticationProviders other than SCRAM-SHA-1 and SCRAM-SHA-256. El Broker Qpid de Apache para Java puede ser configurado para usar diferentes llamados AuthenticationProviders para manejar la autenticación de usuarios. • http://qpid.2158936.n2.nabble.com/CVE-2016-8741-Apache-Qpid-Broker-for-Java-Information-Leakage-td7657025.html http://www.securityfocus.com/bid/95136 http://www.securitytracker.com/id/1037537 https://issues.apache.org/jira/browse/QPID-7599 • CWE-200: Exposure of Sensitive Information to an Unauthorized Actor •
CVE-2016-4432
https://notcve.org/view.php?id=CVE-2016-4432
The AMQP 0-8, 0-9, 0-91, and 0-10 connection handling in Apache Qpid Java before 6.0.3 might allow remote attackers to bypass authentication and consequently perform actions via vectors related to connection state logging. La manipulación de conexión AMQP 0-8, 0-9, 0-91 y 0-10 en Apache Qpid Java en versiones anteriores a 6.0.3 podría permitir a atacantes remotos eludir la autenticación y consecuentemente realizar acciones a través de vectores relacionados con el registro de estado de conexión. • http://mail-archives.apache.org/mod_mbox/qpid-users/201605.mbox/%3CCAFEMS4tXDKYxKVMmU0zTb_7uzduoUS4_RePnUwz1tj%2BGQLNw5Q%40mail.gmail.com%3E http://packetstormsecurity.com/files/137216/Apache-Qpid-Java-Broker-6.0.2-Authentication-Bypass.html http://www.securityfocus.com/archive/1/538508/100/0/threaded http://www.securitytracker.com/id/1035983 https://issues.apache.org/jira/browse/QPID-7257 https://svn.apache.org/viewvc?view=revision&revision=1743161 https://svn.apache.org/viewvc?view=revision&revision= • CWE-287: Improper Authentication •
CVE-2016-3094
https://notcve.org/view.php?id=CVE-2016-3094
PlainSaslServer.java in Apache Qpid Java before 6.0.3, when the broker is configured to allow plaintext passwords, allows remote attackers to cause a denial of service (broker termination) via a crafted authentication attempt, which triggers an uncaught exception. PlainSaslServer.java en Apache Qpid Java en versiones anteriores a 6.0.3, cuando el broker está configurado para permitir contraseñas en texto plano, permite a atacantes remotos provocar una denegación de servicio (terminación del broker) a través de un intento de autenticación manipulado, lo que desencadena una excepción no capturada. • http://mail-archives.apache.org/mod_mbox/qpid-users/201605.mbox/%3C5748641A.2050701%40gmail.com%3E http://packetstormsecurity.com/files/137215/Apache-Qpid-Java-Broker-6.0.2-Denial-Of-Service.html http://qpid.apache.org/releases/qpid-java-6.0.3/release-notes.html http://www.securityfocus.com/archive/1/538507/100/0/threaded http://www.securitytracker.com/id/1035982 https://issues.apache.org/jira/browse/QPID-7271 https://svn.apache.org/viewvc?view=revision&revision=1744403 • CWE-20: Improper Input Validation CWE-287: Improper Authentication •
CVE-2016-2166
https://notcve.org/view.php?id=CVE-2016-2166
The (1) proton.reactor.Connector, (2) proton.reactor.Container, and (3) proton.utils.BlockingConnection classes in Apache Qpid Proton before 0.12.1 improperly use an unencrypted connection for an amqps URI scheme when SSL support is unavailable, which might allow man-in-the-middle attackers to obtain sensitive information or modify data via unspecified vectors. Las clases (1) proton.reactor.Connector, (2) proton.reactor.Container y (3) proton.utils.BlockingConnection en Apache Qpid Proton en versiones anteriores a 0.12.1 usan de forma incorrecta una conexión cifrada para un esquema URI amqps cuando el soporte SSL no está disponible, lo que podría permitir a atacantes man-in-the-middle obtener información sensible o modificar datos a través de vectores no especificados. • http://lists.fedoraproject.org/pipermail/package-announce/2016-April/182414.html http://packetstormsecurity.com/files/136403/Apache-Qpid-Proton-0.12.0-SSL-Failure.html http://qpid.apache.org/releases/qpid-proton-0.12.1/release-notes.html http://www.securityfocus.com/archive/1/537864/100/0/threaded https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git%3Bh=a058585 https://issues.apache.org/jira/browse/PROTON-1157 https://lists.apache.org/thread.html/914424e4d798a340f523b6169aaf39b626971d9bb00fcde • CWE-200: Exposure of Sensitive Information to an Unauthorized Actor •