4 ms·
I would call it an attack if you can inject it into someone's else machine build it and run it as guest (or upload it as a binary and run it). Writing a progra
by tzury 16y ago
I would call it an attack if you can inject it into someone's else machine build it and run it as guest (or upload it as a binary and run it).
Writing a program which eats all available CPU and other resources it is not a big deal, is it?
- nodata 16y agoThere is no good description of the program, but if the program is unkillable, it's an attack. root should be able to kill stuff, if root can't, that's a big deal.
- ENOTTY 16y agoThe big thing is that it's unkillable (even by root) because its chewing CPU while in running kernel code.
- leif 16y agoThere are other ways of gaining remote access. This is a pretty well-constructed local DoS attack you can run (without root access, I think!). Attacks can take many forms, most new attacks are single components that one would combine to perform a real-world attack. Here, you would combine some method of gaining remote access (maybe a webserver hole you can drop a shell with) with this and get an excellent remote DoS attack.
- saurik 16y agoOne really easy way of getting remote access is to ask for it. Local exploits and DoS attacks are important not just because other exploits may let you run code remotely: there are many situations in which computers are not single-user devices. At my university anyone can remotely log in to any of the machines used as lab workstations and there are numerous shared fileservers you can log in to as well. People also still routinely purchase "shell accounts" on shared hosting providers.
- deleted 16y ago[deleted]
- Adaptive 16y agovirtual server instances on a machine with a compromised instance. cpu eater becomes non-trivial.