CVSS: 6.5EPSS: 0%CPEs: 2EXPL: 0CVE-2020-13595
https://notcve.org/view.php?id=CVE-2020-13595
The Bluetooth Low Energy (BLE) controller implementation in Espressif ESP-IDF 4.0 through 4.2 (for ESP32 devices) returns the wrong number of completed BLE packets and triggers a reachable assertion on the host stack when receiving a packet with an MIC failure. An attacker within radio range can silently trigger the assertion (which disables the target's BLE stack) by sending a crafted sequence of BLE packets. La implementación del controlador Bluetooth Low Energy (BLE) en Espressif ESP-IDF versiones 4.0 hasta 4.2 (para dispositivos ESP32) devuelve el número errado de paquetes BLE completados y desencadena una aserción alcanzable en la pila del host cuando está recibiendo un paquete con un fallo de MIC. Un atacante dentro del radio de alcance puede desencadenar silenciosamente la aserción (que deshabilita la pila BLE del objetivo) al enviar una secuencia de paquetes BLE diseñada • https://asset-group.github.io/cves.html https://asset-group.github.io/disclosures/sweyntooth https://github.com/espressif/esp32-bt-lib • CWE-617: Reachable Assertion •
CVSS: 6.5EPSS: 0%CPEs: 2EXPL: 0CVE-2020-13594
https://notcve.org/view.php?id=CVE-2020-13594
The Bluetooth Low Energy (BLE) controller implementation in Espressif ESP-IDF 4.2 and earlier (for ESP32 devices) does not properly restrict the channel map field of the connection request packet on reception, allowing attackers in radio range to cause a denial of service (crash) via a crafted packet. La implementación del controlador Bluetooth Low Energy (BLE) en Espressif ESP-IDF versiones 4.2 y anteriores (para dispositivos ESP32) no restringe apropiadamente el campo channel map del paquete de petición de conexión en la recepción, permitiendo a unos atacantes en el radio de alcance causar una denegación de servicio (bloqueo) por medio de un paquete diseñado • https://asset-group.github.io/cves.html https://asset-group.github.io/disclosures/sweyntooth https://github.com/espressif/esp32-bt-lib • CWE-20: Improper Input Validation •
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: 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 •