Before this happened, many members still believed that malware flashing firmware was an extremely unlikely event.
We might be able to fix this bug, but the real bug is that all running programs on the entire system can gain root privileges, even a custom script. If they have root they can even flash the cfe or other boot partition and if they do they can take control of the router forever because we don't know many things about the cfe and we are even denied to discuss how to flash it.
It won't just happen this time, every router is now a complete computer that can do almost anything, but unlike a computer there is no process to protect it.
If I were a malware author, I would happily hack these devices, these routers can be used for mining, used as a source of DDoS, and also used as a proxy server for hackers because of good performance, ample RAM, and Storage space, I must say these devices are already more powerful than some early Raspberry Pi.
So, why do some people think malware authors don't do this? because we haven't seen a case?
This isn't just for Asuswrt, any brand of router has the same issues these days, excess performance, ample RAM and ROM, almost complete Linxu system, and zero protection there once malware is running on the device.
AiProtection? It is not designed to deal with this kind of threat at all, any user can completely disable all protection features, firewalls on the router with a few nvram commands.
The only way is to ask router manufacturers, not just Asus, all manufacturers to take the systems in their routers seriously, as many don't even update router firmware after a year, like TP-LINK.
They're just selling hardware not firmware, they don't care about firmware, they only care about getting you to buy a more powerful router next year.
I can say that with the policies of the FCC and more closed chip makers, I'm no longer looking forward to running real community-maintained firmware on these routers, OpenWRT, DD-WRT, FreshTomato, all of these in the AX era. dead, they will continue to die in the future. Only manufacturers can save their firmware, and there is no reason for manufacturers to devote resources to firmware maintenance rather than marketing.
Fortunately, Asuswrt-Merlin seems to be the only firmware that is still actively contributed by the community in the AX era. Although more and more components are closed source, thanks to the good relationship between Eric and Asus, we can still use this excellent firmware in the AX era.
But we can't ignore the threats of tomorrow because of security now, we must act to urge and call on router manufacturers to take responsibility for their firmware, or open them up and transfer responsibility to communities.
Read more:
I'm promoting research into CFE (boot partition) for routers and open up research to encourage people to understand CFE and learn how to secure CFE.
https://www.snbforums.com/threads/about-the-cfe-of-hnd-routers.77922/
I was previously proposing to design a suite of anti-malware software for Asuswrt designed to monitor privileged programs running on the system and anything deliberate, but this proposal was not actively supported, it is dead, however, it is ready to be reborn in more If any developers are willing to participate.
http://www.snbforums.com/threads/is...re-program-for-asuswrt-merlin-firmware.76373/