You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I hosted a web-app on jelastic (dogado) as a docker container. After 2 week I get an email:
--- email ---
Dear Jelastic customer,
there was a process of the command "/usr/local/tomcat/3333" which was sending massive packets to different targets this morning. The symptoms look like the docker instance has a security hole and was used in an DDoS attack or part of a botnet.
The top command showed this process:
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
334 root 20 0 104900 968 456 S 99.2 0.1 280:51.95 3333
We have killed the process and changed the permissions of the file:
root@node0815-somename:/# kill 334
root@node0815-somename:/# chmod 000 /usr/local/tomcat/3333
Please investigate or use a more security hardenend docker template.
---email---
Has anyone encountered the same or a similar problem before? Is it possible that the container was hacked?
The text was updated successfully, but these errors were encountered:
The official docker tomcat repo leaves several default tomcat apps in the webapps directory. .
"Tomcat ships with a number of web applications that are enabled by default. Vulnerabilities have been discovered in these applications in the past. Applications that are not required should be removed so the system will not be at risk if another vulnerability is discovered." https://tomcat.apache.org/tomcat-8.0-doc/security-howto.html#Default_web_applications
The official images are kept as close to upstream as possible, users should be familiar with maintainership of the software just as would be required outside of a container environment.
I hosted a web-app on jelastic (dogado) as a docker container. After 2 week I get an email:
--- email ---
Dear Jelastic customer,
there was a process of the command "/usr/local/tomcat/3333" which was sending massive packets to different targets this morning. The symptoms look like the docker instance has a security hole and was used in an DDoS attack or part of a botnet.
The top command showed this process:
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
334 root 20 0 104900 968 456 S 99.2 0.1 280:51.95 3333
root@node0815-somename:/# ls -al /proc/334
...
lrwxrwxrwx 1 root root 0 Jul 26 08:16 cwd -> /usr/local/tomcat
lrwxrwxrwx 1 root root 0 Jul 26 08:16 exe -> /usr/local/tomcat/3333
We have killed the process and changed the permissions of the file:
root@node0815-somename:/# kill 334
root@node0815-somename:/# chmod 000 /usr/local/tomcat/3333
Please investigate or use a more security hardenend docker template.
---email---
Has anyone encountered the same or a similar problem before? Is it possible that the container was hacked?
The text was updated successfully, but these errors were encountered: