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 •
CVSS: 6.9EPSS: 0%CPEs: 2EXPL: 0CVE-2018-18558
https://notcve.org/view.php?id=CVE-2018-18558
An issue was discovered in Espressif ESP-IDF 2.x and 3.x before 3.0.6 and 3.1.x before 3.1.1. Insufficient validation of input data in the 2nd stage bootloader allows a physically proximate attacker to bypass secure boot checks and execute arbitrary code, by crafting an application binary that overwrites a bootloader code segment in process_segment in components/bootloader_support/src/esp_image_format.c. The attack is effective when the flash encryption feature is not enabled, or if the attacker finds a different vulnerability that allows them to write this binary to flash memory. Se descubrió un problema en Espressif ESP-IDF versión 2.x y versión 3.x anterior a 3.0.6 y versión 3.1.x anterior a 3.1.1. La comprobación insuficiente de los datos de entrada en el gestor de arranque de la segunda etapa permite que un atacante físicamente próximo omita las comprobaciones de arranque seguras y ejecute código arbitrario, creando un binario de aplicación que sobrescriba un segmento de código del gestor de arranque en el parámetro process_segment en el archivo components/bootloader_support/src/esp_image_format.c. • https://github.com/espressif/esp-idf/releases https://www.espressif.com/en/news/Espressif_Product_Security_Advisory_Concerning_Secure_Boot_%28CVE-2018-18558%29 • CWE-20: Improper Input Validation •