If you circle around a building you can easily find where a router is hidden. The first flaw is the simplest, and only effects ESP8266s. If there isn’t one, why would they do it? I don’t think that Espressif did anything to aid this hack. Case in point: the low-level WiFi firmware. :) To save code (memory is always in short supply) many of those handlers share routines, and ownership gets muddy. Security is much harder to measure, so it is easier to make a mistake. ESP32 / 8266 WiFi Signal Strength: Do you know about the WiFi signal strength from an ESP? They barely have any modern stack hardening and no ASLR or nx pages. Why don’t firmware programmers think that things may go wrong? This bug patching is LOOOOONG overdue for the EAP “support” on the ESP. Nobody looks cause there are no valuable targets.. There are already about 50 instructables on how to do mass death with a esp8266 so this really changes nothing from that perspective. Some ESP32/ESP8266 3D printers may be in danger xD. == 6) == (3 != 6) and in this case, the spaces are part of the syntax. Nor that they will ever receive a patch…. and they’ve patched around most of the vulnerabilities already, but if you’re running software on any of these chips that’s in a critical environment, you’d better push up new firmware pretty quick. This procedure is a useful example, as it is similar to all other types of microcontrollers. Watch the video on my channel to see the board in action! The people who should be concerned with upgrading their firmware are those who have integrated ESP32/8266s into their commercial products, their business-critical applications, and their homes. Jay Phantom liked A 10X 100MHz Differential Probe. To answer these questions, I performed several tests comparing various types of microcontrollers, including ESP32 with ESP8266. Putting the responsibility at the start of the chain is asking for trouble. There are details for the constructor where we can define the CHANNEL in which the created network will operate. The SDK layer is fully open source. It is actually in the app where to ON command comes from.Need someone to download the app and see how they created code inside. (I need someone to use the ’32 to cure pattern baldness…). This takes advantage of the ESP’s packet injection mode, which we’ve covered before. If it is authorized, then the app to use and monitor the device will turn on the ESP32 chip. The same could be done with virtually any router, etc. its up the community to not be dumb and start publishing easy to follow jamming instructions and code for any pissed off skid can replicate for the good of the creators of this wonderful chip and the future of full foss and osh. Time for a petition to ask them to release the sources of their wifi stack, or a leak of their proprietary source code. The apocalypse never came. All chips were connected simultaneously, side by side. Been done long time ago. One hack makes the ESP32 or ESP8266 on the EAP-enabled network crash, but the other hack allows for a complete hijacking of the encrypted session. An SDK patch does not mean the 100.000.000 devices already out there are patched. He notified Espressif first (thanks!) */ I don’t want to find this used for spamming and spoofing, I want to see mesh networks and solar bridges! With this unholy mixture of symbology, somebody’s head is going to explode, because (3! danjovic, you might take offense that I’m explaining obvious things, but since you asked the question, I’m going to answer it in earnest. Perhaps in a idealistic future when we have all moved from c/c++ to Rust at the firmware level many of these memory/buffer bugs will be caught by the compiler, and mere mortal programmers will produce better code.