Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


Shells Virtual Desktop
BMail.ag - Secure Email Service
Server.net
CPLicense.net
VPS Server
Buy VPN
Vultr
VMs for AI
HostDare
ReliableSite White-Label Dedicated Hosting for Resellers
InterServer VPS
BMail.ag - Secure Email Service
Best VPN
High-Performance Bare Metal Server Solutions
Karvl.com
Server Mania Cloud Hosting
DataWagon Hosting
AlphaVPS Hosting
Evoxt.com
Clouvider
VPS Hosting with NVMe
Residential IPs in the US & 4G Mobile Proxies in EU & US with Unlimited Bandwidth
ReliableSite White-Label Dedicated Hosting for Resellers
Rabisu - Hosting Solutions
Shells Virtual Desktop
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

Dirty Frag: Universal Linux LPE

13»

Comments

  • forestforest Member

    @mustafamw3 said: On a typical web hosting server without IPsec/VPN usage, there usually isn’t anything triggering esp4, esp6, or rxrpc during normal operation.

    "During normal operation" is the key point. During normal operation, no one is going to be attempting an LPE either. But if anything is compromised, say an NTP daemon or a recursive DNS resolver, it could trigger module loading and then exploit the system. In essence, even if the modules are not loaded, every single process on the system is running as root.

  • mustafamw3mustafamw3 Member, Patron Provider, LIR
    edited May 9

    @forest said:

    @mustafamw3 said: On a typical web hosting server without IPsec/VPN usage, there usually isn’t anything triggering esp4, esp6, or rxrpc during normal operation.

    "During normal operation" is the key point. During normal operation, no one is going to be attempting an LPE either. But if anything is compromised, say an NTP daemon or a recursive DNS resolver, it could trigger module loading and then exploit the system. In essence, even if the modules are not loaded, every single process on the system is running as root.

    That’s fair, and I understand your point.

    If an attacker already compromised something like an NTP daemon or recursive DNS resolver enough to execute code and interact with kernel functionality, then you already have a serious security problem other than Dirty Frag itself.

  • forestforest Member

    @mustafamw3 said:

    @forest said:

    @mustafamw3 said: On a typical web hosting server without IPsec/VPN usage, there usually isn’t anything triggering esp4, esp6, or rxrpc during normal operation.

    "During normal operation" is the key point. During normal operation, no one is going to be attempting an LPE either. But if anything is compromised, say an NTP daemon or a recursive DNS resolver, it could trigger module loading and then exploit the system. In essence, even if the modules are not loaded, every single process on the system is running as root.

    That’s fair, and I understand your point.

    If an attacker already compromised something like an NTP daemon or recursive DNS resolver enough to execute code and interact with kernel functionality, then you already have a serious security problem other than Dirty Frag itself.

    That's true, and that's why defense in depth is such a good idea. Otherwise, we'd all just run everything as root and mode 777 everything.

    Thanked by 2mustafamw3 bjo
Sign In or Register to comment.