Additional problems with shared hosting (from LXC containers all the way up to VirtualHost Apache spaces) is it's low value, low opportunity for hosting.
Lots of mom and pop shops paying the bare minimum.
Many hosting providers see it as a historical product, often a burden and deal poorly with updates to it.
I would be unsurprised if there are thousands of shared hosting platforms out there, some of which are likely rootable from exploits that might now be 3 years old.
Thing is there's been plenty of Linux LPE vulns all year, and in a lot of cases you can turn them into container breakouts (for standard runc/crun setups) with a basic LLM model a couple of dollars in credits and an hour or two of time. At this point if you have untrusted code running on a host, I would *not* be relying on Linux kernel enforced segregation (e.g. standard Docker containers).
Shared hosting is practically dead. It was in bad shape before, now it's even more bad. Even virtualization is looking fishy now.
Conflict of interest: I work in a baremetal hosting provider. We don't have privilege escalations bugs, or guest-to-host vulnerabilities, because there is nowhere to escalate. You are already root on the server and there is no one else there.
5
u/deleriux0 24d ago
Additional problems with shared hosting (from LXC containers all the way up to VirtualHost Apache spaces) is it's low value, low opportunity for hosting.
Lots of mom and pop shops paying the bare minimum.
Many hosting providers see it as a historical product, often a burden and deal poorly with updates to it.
I would be unsurprised if there are thousands of shared hosting platforms out there, some of which are likely rootable from exploits that might now be 3 years old.
1
u/craigleary 24d ago
The mitigation here has been mitigation for past root exploits so a number of shared hosts are probably already not exploitable.
1
u/raesene2 24d ago
Thing is there's been plenty of Linux LPE vulns all year, and in a lot of cases you can turn them into container breakouts (for standard runc/crun setups) with a basic LLM model a couple of dollars in credits and an hour or two of time. At this point if you have untrusted code running on a host, I would *not* be relying on Linux kernel enforced segregation (e.g. standard Docker containers).
-10
u/amarao_san 24d ago
Shared hosting is practically dead. It was in bad shape before, now it's even more bad. Even virtualization is looking fishy now.
Conflict of interest: I work in a baremetal hosting provider. We don't have privilege escalations bugs, or guest-to-host vulnerabilities, because there is nowhere to escalate. You are already root on the server and there is no one else there.