3 ms·
I don't disagree in principle. In practice: how did they manage to start their own daemon on a port sshd is already bound to?
by staunch 16y ago
I don't disagree in principle. In practice: how did they manage to start their own daemon on a port sshd is already bound to?
- cd34 16y agoWeb exploit, get a web shell, crash your ssh daemon somehow, start my own. Since it is running on a non-privileged port, easy enough to run my own ssh daemon there. Crashing the ssh daemon isn't always easy, but, making the job easier for an attacker because 'obscurity' is considered a good protection scheme in this case opens up other potential vulnerabilities.
- JoachimSchipper 16y agoLinux' OOM killer, just to give one possible example.