-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
logrotate inside the container causes all CPU cores 100% - probable malware #134
Comments
The mallware is back/still here (after a week of scrubbing). So I tested my system and I even created the service to automatically delete the malware process but obviously someone is trying to start his fake .logrotate on my system through this docker image. I checked everything and did all by the book even scrubbing the system and reinstalling caused this. Obviously the "hacker" noticed he got detected and he tried to hide the process by adding the
|
I am certainly no expert, and cannot even say if this is malware or not. But reviewing the Dockerfile, a plausible explanation for a possible breach is the dependency on the base docker image (eclipse-temurin:17-jdk-jammy). The Dockerhub repository indicates several known vulnerabilities of this image. Might it be possible to resort to better maintaned OpenJDKs (https://hub.docker.com/_/openjdk)? @fugasjunior Just an Idea, no qualified solution |
It seems update v1.4.0 helped with the issue by updating the dependencies. I'll keep this issue open for some time if anyone still has the problem even after the update, but for now, it seems solved. |
Have literally the same issue. What the update are you talking about? And is it still helping? |
Describe the bug
After a while containered logrotate in /root/.config/logrotate starts. It is not an standard logrotate file location and the executable seems not to be real logrotate (maybe a miner or some other malware). Servers are affected by the malicious logrotate (high lag spikes due CPU issues).
To Reproduce
Steps to reproduce the behavior:
Start the server and the problem will start randomly after few hours of activty.
Expected behavior
It should not run. Server should not be affected by logrotate (it should be just an ordinary log rotation utility)
Screenshots
This is the containered process tree running /root/.config/logrotate
First-aid
Killed the process's and removed the executable. Still waiting to see if the container will reaquire the executable. After the process termination cores are back to normal and servers are running fine. Zombie process inside container stays active.
EDIT:
After 3 hours the executable reappeared in /root/.config/logrotate and was executed inside container
So yeah I am now 100% sure this docker image contains malware.
Environment
OS: Ubuntu 22.04
docker-compose.yml
Standard docker compose no modifications, only sensitive data change.
.env
standard env no modifications.
The text was updated successfully, but these errors were encountered: