CVSS: 6.8EPSS: 0%CPEs: 3EXPL: 1CVE-2020-12638
https://notcve.org/view.php?id=CVE-2020-12638
An encryption-bypass issue was discovered on Espressif ESP-IDF devices through 4.2, ESP8266_NONOS_SDK devices through 3.0.3, and ESP8266_RTOS_SDK devices through 3.3. Broadcasting forged beacon frames forces a device to change its authentication mode to OPEN, effectively disabling its 802.11 encryption. Se detectó un problema de omisión de cifrado en dispositivos Espressif ESP-IDF versiones hasta 4.2, dispositivos ESP8266_NONOS_SDK versiones hasta 3.0.3 y dispositivos ESP8266_RTOS_SDK versiones hasta 3.3. La transmisión de tramas beacon forjadas obliga a un dispositivo a cambiar su modo de autenticación a OPEN, deshabilitando efectivamente su encriptación 802.11 • https://github.com/espressif/ESP8266_NONOS_SDK https://github.com/espressif/ESP8266_RTOS_SDK https://github.com/espressif/esp-idf https://lbsfilm.at/blog/wpa2-authenticationmode-downgrade-in-espressif-microprocessors • CWE-287: Improper Authentication CWE-319: Cleartext Transmission of Sensitive Information •
CVSS: 4.6EPSS: 0%CPEs: 8EXPL: 0CVE-2019-17391
https://notcve.org/view.php?id=CVE-2019-17391
An issue was discovered in the Espressif ESP32 mask ROM code 2016-06-08 0 through 2. Lack of anti-glitch mitigations in the first stage bootloader of the ESP32 chip allows an attacker (with physical access to the device) to read the contents of read-protected eFuses, such as flash encryption and secure boot keys, by injecting a glitch into the power supply of the chip shortly after reset. Se descubrió un problema en el código ROM de la máscara de Espressif ESP32 08-06-2016 desde 0 hasta 2. La falta de mitigaciones contra fallos en el cargador de arranque de la primera etapa del chip ESP32 permite a un atacante (con acceso físico al dispositivo) leer el contenido de eFuses protegidos contra lectura, tales como el cifrado flash y las claves de arranque seguras, al inyectar un fallo en la fuente de alimentación del chip poco después del reinicio. • https://www.espressif.com/en/news/Security_Advisory_Concerning_Fault_Injection_and_eFuse_Protections • CWE-755: Improper Handling of Exceptional Conditions •
CVSS: 7.2EPSS: 0%CPEs: 4EXPL: 0CVE-2019-15894
https://notcve.org/view.php?id=CVE-2019-15894
An issue was discovered in Espressif ESP-IDF 2.x, 3.0.x through 3.0.9, 3.1.x through 3.1.6, 3.2.x through 3.2.3, and 3.3.x through 3.3.1. An attacker who uses fault injection to physically disrupt the ESP32 CPU can bypass the Secure Boot digest verification at startup, and boot unverified code from flash. The fault injection attack does not disable the Flash Encryption feature, so if the ESP32 is configured with the recommended combination of Secure Boot and Flash Encryption, then the impact is minimized. If the ESP32 is configured without Flash Encryption then successful fault injection allows arbitrary code execution. To protect devices with Flash Encryption and Secure Boot enabled against this attack, a firmware change must be made to permanently enable Flash Encryption in the field if it is not already permanently enabled. • https://www.espressif.com/en/news/Espressif_Security_Advisory_Concerning_Fault_Injection_and_Secure_Boot • CWE-755: Improper Handling of Exceptional Conditions •
CVSS: 6.5EPSS: 0%CPEs: 6EXPL: 2CVE-2019-12586
https://notcve.org/view.php?id=CVE-2019-12586
The EAP peer implementation in Espressif ESP-IDF 2.0.0 through 4.0.0 and ESP8266_NONOS_SDK 2.2.0 through 3.1.0 processes EAP Success messages before any EAP method completion or failure, which allows attackers in radio range to cause a denial of service (crash) via a crafted message. La implementación de peer EAP en Espressif ESP-IDF versiones 2.0.0 hasta 4.0.0 y ESP8266_NONOS_SDK versiones 2.2.0 hasta 3.1.0, procesa los mensajes EAP Success antes de cualquier completación o fallo del método EAP, lo que permite a los atacantes en un radio de alcance causar una denegación de servicio (bloqueo) por medio de un mensaje diseñado. • https://github.com/Matheus-Garbelini/esp32_esp8266_attacks https://github.com/espressif https://matheus-garbelini.github.io/home/post/esp32-esp8266-eap-crash •
CVSS: 8.1EPSS: 0%CPEs: 2EXPL: 1CVE-2019-12587
https://notcve.org/view.php?id=CVE-2019-12587
The EAP peer implementation in Espressif ESP-IDF 2.0.0 through 4.0.0 and ESP8266_NONOS_SDK 2.2.0 through 3.1.0 allows the installation of a zero Pairwise Master Key (PMK) after the completion of any EAP authentication method, which allows attackers in radio range to replay, decrypt, or spoof frames via a rogue access point. La implementación de un peer EAP en Espressif ESP-IDF versiones 2.0.0 hasta 4.0.0 y ESP8266_NONOS_SDK versiones 2.2.0 hasta 3.1.0, permite la instalación de una Pairwise Master Key (PMK) cero después de la completación de cualquier método de autenticación EAP, lo que permite a atacantes dentro de un radio de alcance reproducir, descifrar o falsificar cuadros por medio de un punto de acceso malicioso. • https://github.com/Matheus-Garbelini/esp32_esp8266_attacks https://github.com/espressif https://matheus-garbelini.github.io/home/post/zero-pmk-installation • CWE-327: Use of a Broken or Risky Cryptographic Algorithm •