-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Security - CVE-2019-12586, CVE-2019-12587, CVE-2019-12588? #6348
Comments
Tasmota uses the Arduino SDK for the ESP82xx. Tasmota can be compiled with different Cores (2.3.0, 2.4.x, 2.5.x, pre-2.6). If the vulnerability is in the particular Core, then Tasmota will likely be affected. |
Hi, Thanks a lot for sharing this information. By default, Tasmota don't use SDK 3.x and for the latests arduino cores, it uses SDK 2.2y that doesn't have enterprise network support. So, the precompiled bins should be fine. The SDK 3.x has several bugs that also have wifi disconnections, that is why is not used by default in Tasmota. |
As explained in the Arduino Repository, (esp8266/Arduino#6436 (comment)) using core 2.5.2 you can have the beacon crash attack. If you use latest STAGE core, this is already fixed. In Tasmota you will need to compile under core pre2.6.0. At this moment this core is the default in platformio.ini |
Hello, thanks for the discussion. I've updated the blog descriptions with all the dates and commit patches that fixes the issues. Espressif has also made backports:
|
Thanks a lot for reporting. Very appreciated. Closing this issue as it is solved by using latest arduino core. Platform.ini file has already this latest core by default: May be we can deploy a new release version with core pre2.6.0? |
( keeping this issue opened until we have patched release binaries available for download ) |
Added http://thehackbox.org/tasmota/json/ to build dev bins using @Jason2866 's modified version of the staged Arduino core. |
Cool, Thanks! 👍 |
BUG DESCRIPTION
I can't find any information on whether the current version is impacted by CVE-2019-12586, CVE-2019-12587 or CVE-2019-12588. The first two appear to be limited to networks with EAP (which I don't think is supported?), but the 3rd appears to be a general vulnerability to crash the esp8266
The issues are described in detail at https://github.com/Matheus-Garbelini/esp32_esp8266_attacks - excerpt:
Follow the links on each vulnerability for more details.
This vulnerabilities were found in SDKs of ESP32 and ESP8266. Their version were ESP-IDF v4.0-dev-459-g7a31cb7 and NONOS-SDK v3.0-103-g7a31cb7 respectivelly at the time of the vulnerabilities discovery.
The text was updated successfully, but these errors were encountered: