3 ms·
Learn from the mistakes of others, do not do this. Remember Yevgeniy Nikulin?
by ryanisnan 4y ago
Learn from the mistakes of others, do not do this. Remember Yevgeniy Nikulin?
- KomoD 4y agoWhat relevance does Yevgeniy Nikulin have with this, whatsoever?
- ryanisnan 4y agoA lot, actually. He compromised a home-ran webserver on a VM, and compromised his way to a networked work machine. Running exposed ports from your house, no matter how smart you think you are, is not a good idea.
- KomoD 4y agoThanks for the explainer.
- hbogert 4y agoWhat's fundamentally different if you host this in the cloud but still have a public port? What was the exact attack vector in the case of nyevgeny?
- ryanisnan 4y agoThe difference is it would be likely inconsequential if a the cloud resource running this was compromised. There’s no direct link (at least there shouldn’t be) to a work machine, which might have credentials or itself VPN information for an employer. Yevgeny did exactly this. He compromised a web server running Apache or something, used that to brute force his way into a networked work machine, which took weeks, but went undetected. That machine turned out to be the physical host the VM running the web server was on. Then he used the work machine to break into LinkedIn using credentials and VPN profiles found on the iMac. This vector would have been impossible had that open server not been running so close to the work machine.