3.0.0.4.386_51955 update available through router interface but no download or any details on ASUS UK website yet.
Will update post once released on the website.
The RT-AC86U is listed as one of the 7 affected routers and yet the CVE-2024-3080 issue was fixed in the 29 March 2024 firmware release. In fact, all 7 hade this issue fixed in March and April, so don't understand why this is being reported on in June.
Just when I thought it was EOL and switched to Merlin....
Version 3.0.0.4.386_51925
66.2 MB
2024/03/29
- Fixed command injection vulnerability.
- Fixed the ARP poisoning vulnerability. Thanks to the contribution of Xin'an Zhou.
- Fixed code execution in custom OVPN. Thanks to the contrubution...
I only have issues with the 5 GHz channel switching randomly from the channel I set (probably because DFS channel), however a reboot will keep it in place for a while.
I also got rid of the ASUS app and disabled web access from WAN as I noticed multiple router login attempts from random IPs in...
Version 3.0.0.4.386_51915
66.13 MB
2023/07/10
Security updates:
-Fixed the cfg server vulnerability.
-Fixed the vulnerability in the logmessage function CVE-2023-35086/ CVE-2023-35087.
-Fixed lighttpd vulnerability, CVE-2023-35720.
-Fixed several curl vulnerabilities including CVE-2023-28322...
Firmware updated today. For me HTTPS router login no longer works on either Chrome or MS Edge, where it did work on MS Edge with previous firmware but not Chrome.
EDIT: I just noted the following text on https://www.asus.com/support/FAQ/1045854/ stating "The default certificate in the router is...
Yep, rebooted and all. In the end did a factory reset and that resolved the issue, however generic router HTTPS certificate still invalid in Google Chrome.
I know others have had this invalid certificate issue in Chrome, but not in MS Edge or Firefox. Did submit to ASUS support asking if there...
One of those days...
The generic HTTPS certificate generated in my RT-AC86U stopped being valid in Google Chrome so I thought I'd try the Let's Encrypt certificate. Created host name in the WAN>DDNS tab, registered it, generated the Let's Encrypt certificate and all worked fine...until I...
@QuozL
Had same problem with Chrome but not MS Edge. Seems to be a recent change to Chrome and a temporary solution is available here https://support.google.com/chrome/a/thread/185950857/net-err-cert-invalid-in-chrome-but-not-in-edge-chromium?hl=en-au
The reason for the change in Chrome is...