Yes, when the setup was up and running, I had closed every port, verified further by nmap, and did only allow incoming 80 and outgoing 80 (egress filtering via apf-firewall). Proxmox ports had only been allowed for my ip. All is possible: Maybe a zero-day between floods against the server...
No. 2 Installations, two compromises within minutes. The only thing I know it is not Proxmox related as I also did another run with plain Debian 7. The problem is there are too much possibilities and to less time to figure things out, as usual.
I have a standard vmbr0 setup with only containers that use venet devices.
One container with it's own IP address has a webserver where I detected that it answers requests with a javascript redirect and can act like a proxy to the webserver itself.
I thought and hoped only the container is...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.