Page 3 of 13 results (0.002 seconds)

CVSS: 5.3EPSS: 0%CPEs: 10EXPL: 0

CVE-2017-8213

https://notcve.org/view.php?id=CVE-2017-8213

Huawei SMC2.0 with software of V100R003C10, V100R005C00SPC100, V100R005C00SPC101B001T, V100R005C00SPC102, V100R005C00SPC103, V100R005C00SPC200, V100R005C00SPC201T, V500R002C00, V600R006C00 has an input validation vulnerability when handle TLS and DTLS handshake with certificate. Due to the insufficient validation of received PKI certificates, remote attackers could exploit this vulnerability to crash the TLS module. Huawei SMC 2.0 con software V100R003C10, V100R005C00SPC100, V100R005C00SPC101B001T, V100R005C00SPC102, V100R005C00SPC103, V100R005C00SPC200, V100R005C00SPC201T, V500R002C00 y V600R006C00 tiene una vulnerabilidad de validación de entradas al gestionar una negociación TLS y DTLS con un certificado. Debido a la insuficiente validación de los certificados PKI recibidos, los atacantes remotos pueden explotar esta vulnerabilidad para cerrar inesperadamente el módulo TLS. • http://www.huawei.com/en/psirt/security-advisories/huawei-sa-20170705-01-tls-en • CWE-295: Improper Certificate Validation •

CVSS: 6.8EPSS: 0%CPEs: 110EXPL: 0

CVE-2017-8163

https://notcve.org/view.php?id=CVE-2017-8163

AR120-S with software V200R006C10, V200R007C00, V200R008C20, V200R008C30,AR1200 with software V200R006C10, V200R006C13, V200R007C00, V200R007C01, V200R007C02, V200R008C20, V200R008C30,AR1200-S with software V200R006C10, V200R007C00, V200R008C20, V200R008C30,AR150 with software V200R006C10, V200R007C00, V200R007C01, V200R007C02, V200R008C20, V200R008C30,AR150-S with software V200R006C10, V200R007C00, V200R008C20, V200R008C30,AR160 with software V200R006C10, V200R006C12, V200R007C00, V200R007C01, V200R007C02, V200R008C20, V200R008C30,AR200 with software V200R006C10, V200R007C00, V200R007C01, V200R008C20, V200R008C30,AR200-S with software V200R006C10, V200R007C00, V200R008C20, V200R008C30,AR2200 with software V200R006C10, V200R006C13, V200R006C16PWE, V200R007C00, V200R007C01, V200R007C02, V200R008C20, V200R008C30,AR2200-S with software V200R006C10, V200R007C00, V200R008C20, V200R008C30,AR3200 with software V200R006C10, V200R006C11, V200R007C00, V200R007C01, V200R007C02, V200R008C00, V200R008C10, V200R008C20, V200R008C30,AR510 with software V200R006C10, V200R006C12, V200R006C13, V200R006C15, V200R006C16, V200R006C17, V200R007C00, V200R008C20, V200R008C30,NetEngine16EX with software V200R006C10, V200R007C00, V200R008C20, V200R008C30,SMC2.0 with software V100R003C10, V100R005C00, V500R002C00, V600R006C00,SRG1300 with software V200R006C10, V200R007C00, V200R007C02, V200R008C20, V200R008C30,SRG2300 with software V200R006C10, V200R007C00, V200R007C02, V200R008C20, V200R008C30,SRG3300 with software V200R006C10, V200R007C00, V200R008C20, V200R008C30 have an out-of-bounds read vulnerability. Due to insufficient input validation, an authenticated, remote attacker could send specially crafted message to the target device.Successful exploit of the vulnerability could cause out-of-bounds read and system crash. AR120-S con software V200R006C10, V200R007C00, V200R008C20, V200R008C30; AR1200 con software V200R006C10, V200R006C13, V200R007C00, V200R007C01, V200R007C02, V200R008C20, V200R008C30; AR1200-S con software V200R006C10, V200R007C00, V200R008C20, V200R008C30; AR150 con software V200R006C10, V200R007C00, V200R007C01, V200R007C02, V200R008C20, V200R008C30; AR150-S con software V200R006C10, V200R007C00, V200R008C20, V200R008C30; AR160 con software V200R006C10, V200R006C12, V200R007C00, V200R007C01, V200R007C02, V200R008C20, V200R008C30; AR200 con software V200R006C10, V200R007C00, V200R007C01, V200R008C20, V200R008C30; AR200-S con software V200R006C10, V200R007C00, V200R008C20, V200R008C30; AR2200 con software V200R006C10, V200R006C13, V200R006C16PWE, V200R007C00, V200R007C01, V200R007C02, V200R008C20, V200R008C30; AR2200-S con software V200R006C10, V200R007C00, V200R008C20, V200R008C30; AR3200 con software V200R006C10, V200R006C11, V200R007C00, V200R007C01, V200R007C02, V200R008C00, V200R008C10, V200R008C20, V200R008C30; AR510 con software V200R006C10, V200R006C12, V200R006C13, V200R006C15, V200R006C16, V200R006C17, V200R007C00, V200R008C20, V200R008C30; NetEngine16EX con software V200R006C10, V200R007C00, V200R008C20, V200R008C30; SMC2.0 con software V100R003C10, V100R005C00, V500R002C00, V600R006C00; SRG1300 con software V200R006C10, V200R007C00, V200R007C02, V200R008C20, V200R008C30; SRG2300 con software V200R006C10, V200R007C00, V200R007C02, V200R008C20, V200R008C30; y SRG3300 con software V200R006C10, V200R007C00, V200R008C20, V200R008C30 tienen una vulnerabilidad de lectura fuera de límites. A causa de una validación de entradas insuficiente, un atacante remoto autenticado podría enviar un mensaje especialmente manipulado al dispositivo objetivo. Una explotación exitosa de esta vulnerabilidad podría provocar una lectura fuera de límites y el cierre inesperado del sistema. • http://www.huawei.com/en/psirt/security-advisories/huawei-sa-20171018-01-h323-en • CWE-125: Out-of-bounds Read •

CVSS: 5.0EPSS: 0%CPEs: 160EXPL: 0

CVE-2015-2808 – SSL/TLS: "Invariance Weakness" vulnerability in RC4 stream cipher

https://notcve.org/view.php?id=CVE-2015-2808

The RC4 algorithm, as used in the TLS protocol and SSL protocol, does not properly combine state data with key data during the initialization phase, which makes it easier for remote attackers to conduct plaintext-recovery attacks against the initial bytes of a stream by sniffing network traffic that occasionally relies on keys affected by the Invariance Weakness, and then using a brute-force approach involving LSB values, aka the "Bar Mitzvah" issue. El algoritmo RC4, utilizado en el protocolo TLS y el protocolo SSL, no combina correctamente los datos de estados con los datos de claves durante la fase de inicialización, lo que facilita a atacantes remotos realizar ataques de recuperación de texto claro contra los bytes iniciales de un flujo mediante la captura de trafico de la red que ocasionalmente depende de claves afectadas por la debilidad de la invariabilidad (Invariance Weakness), y posteriormente utilizar un acercamiento de fuerza bruta que involucra valores LSB, también conocido como el problema de 'Bar Mitzvah'. • http://h20564.www2.hpe.com/hpsc/doc/public/display?docId=emr_na-c04779034 http://kb.juniper.net/InfoCenter/index?page=content&id=JSA10705 http://kb.juniper.net/InfoCenter/index?page=content&id=JSA10727 http://lists.opensuse.org/opensuse-security-announce/2015-06/msg00013.html http://lists.opensuse.org/opensuse-security-announce/2015-06/msg00014.html http://lists.opensuse.org/opensuse-security-announce/2015-06/msg00015.html http://lists.opensuse.org/opensuse-security-announce/2015-06/msg00022.html • CWE-327: Use of a Broken or Risky Cryptographic Algorithm •