Exploiting those vulnerabilities via pure network traffic is borderline impossible. Most CPU exploits (meltdown et al.) require execution on the device, you can’t do it via crafted network packets.
I can’t think of any typical services that you’d run on a router/home server that allow arbitrary code execution. The main risk was mostly web browsers with JavaScript, or VPS providers.
Either way, definitely unlikely for a home router.
I hear you, I host lots of stuff. But none I can think of would be RCE vulnerable directly from a CPU vulnerability. You could use a CPU vulnerability to privesc later, but once someone has RCE, your already pwn’d, and privesc is mostly a given anyway either way. So CPU vulnerabilities falls way down the list of things to worry about.
As long as you keep your router OS patched and up to date, CPU vulns really arent a concern.
deleted by creator
Exploiting those vulnerabilities via pure network traffic is borderline impossible. Most CPU exploits (meltdown et al.) require execution on the device, you can’t do it via crafted network packets.
deleted by creator
I can’t think of any typical services that you’d run on a router/home server that allow arbitrary code execution. The main risk was mostly web browsers with JavaScript, or VPS providers.
Either way, definitely unlikely for a home router.
deleted by creator
I hear you, I host lots of stuff. But none I can think of would be RCE vulnerable directly from a CPU vulnerability. You could use a CPU vulnerability to privesc later, but once someone has RCE, your already pwn’d, and privesc is mostly a given anyway either way. So CPU vulnerabilities falls way down the list of things to worry about.
As long as you keep your router OS patched and up to date, CPU vulns really arent a concern.
deleted by creator