A critical vulnerability (CVE-2024-5035) has been disclosed in the TP-Link Archer C5400X gaming router, allowing remote code execution.
The Article
A maximum-severity security flaw has been disclosed in the TP-Link Archer C5400X gaming router that could lead to remote code execution on susceptible devices by sending specially crafted requests. The vulnerability, tracked as CVE-2024-5035, carries a CVSS score of 10.0. It impacts all versions of the router firmware including and prior to 1_1.1.6. It has been patched in version 1_1.1.7 released on May 24, 2024.
"By successfully exploiting this flaw, remote unauthenticated attackers can gain arbitrary command execution on the device with elevated privileges," German cybersecurity firm ONEKEY said in a report published Monday. The issue is rooted in a binary related to radio frequency testing "rftest" that's launched on startup and exposes a network listener on TCP ports 8888, 8889, and 8890, thus allowing a remote unauthenticated attacker to achieve code execution. While the network service is designed to only accept commands that start with "wl" or "nvram get," ONEKEY found that the restriction could be trivially bypassed by injecting a command after shell meta-characters like ; , & , or, | (e.g., "wl;id;").
Cybersecurity
TP-Link's implemented fix in version 1_1.1.7 Build 20240510 addresses the vulnerability by discarding any command containing these special characters. "It seems the need to provide a wireless device configuration API at TP-Link had to be answered either fast or cheap, which ended up with them exposing a supposedly limited shell over the network that clients within the router could use as a way to configure wireless devices," ONEKEY said.
The disclosure arrives weeks after security flaws were also revealed by the company in Delta Electronics DVW W02W2 industrial Ethernet routers (CVE-2024-3871) and Ligowave networking gear (CVE-2024-4999) that could allow remote attackers to gain remote command execution with elevated privileges. It's worth noting that these flaws remain unpatched due to the devices being no longer actively maintained, making it imperative that users take adequate steps to limit exposure of administration interfaces to reduce the potential for exploitation.
They also buy it because it is marketed for gamers telling them it gives them an advantage. Which it will if you compare it to a shitty router from 2008. Nowadays any mainstream router will do fine as long as you are within its range. If you really care as a gamer use a wired connection.
While the network service is designed to only accept commands that start with “wl” or “nvram get,” ONEKEY found that the restriction could be trivially bypassed by injecting a command after shell meta-characters like ; , & , or, | (e.g., “wl;id;”).
Whenever I feel like I'm a terrible programmer, I remind myself that there are vast amounts of confident coders out there being paid for code with idiotic mistakes like this and they have no intention of getting any better at it
Frankly " injecting a command after shell-metacharacters" makes it sound much more mystical and arcane than"just use the normal one liner syntax to run 2 commands"
Leaving consumer routers behind and going the pfSense route is among the best decisions I've ever made. Highly recommended for anyone who isn't afraid to learn some network stuff.
Same idea here. Fortigate 30f (since I can dl updates manually), Fortiswitch 124e (same) and 2 FortiAP 421E's (ditto).
All but ap's I could grab from employers "ditch bin".
I'm running a Pentium G4560 and 8Gb of RAM in a dual NIC Shuttle case. The specs were a total gamble but I have a lot of headroom currently so if I need to do more advanced stuff in the future I can.
Setting up a pfsense router / firewall virtualized in proxmox on my server PC with separate vlans for my iot devices and guest WiFi was tedious, time consuming, challenging, educational, and ultimately worth it. I'm not invincible buy at least I have fucking viability into what's going on in my fucking home network.
Do you have any recommendations for someone looking to do this? Guides you found useful, videos or YouTube channels, software packages, pitfalls to avoid? I've been thinking of doing something like this for years and lately feel like I need to to get a handle on what's really going on in my network
I remember that anticipation fondly. 😁 I watched a bunch of videos on pfSense (Lawrence Systems on YT is great, but you probably know that already) and read a bunch of things, planning out what I wanted to do before I made the leap, and it was great!