Skip to content
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

Random Data Base Drop In Docker Container. #1157

Closed
rranjangupta opened this issue Dec 3, 2023 · 2 comments
Closed

Random Data Base Drop In Docker Container. #1157

rranjangupta opened this issue Dec 3, 2023 · 2 comments

Comments

@rranjangupta
Copy link

Description:
I encountered a series of errors and failures on the PostgreSQL server, possibly indicating various issues with the system setup or configurations. Below is a log of the errors encountered:

Server Information:

PostgreSQL Version: 16.0 (Debian 16.0-1.pgdg120+1)
OS: Debian 12.2.0, 64-bit
Error Messages:

Logs indicate missing executables (pkill, ufw, iptables, curl, etc.).
Permission denied errors (/etc/sysctl.conf, /usr/local/bin/curl, /etc/ld.so.preload, etc.).
Invalid length of startup packets.
Connection/authentication failures for various users (postgres, KRwc, etc.).
Database "orchestrator" does not exist.
Actions Tried:

Attempts to execute various commands that resulted in failures.
Connection attempts with different protocols showing "unsupported frontend protocol."
Impact:

The errors seem to affect database connectivity, user authentication, and system commands, potentially impacting system stability and functionality.
Suspected Causes:

Missing executables, permission issues on critical files, incorrect configurations in PostgreSQL or system-wide settings.
Uploading postgresql-2023-12-01_080337.log…

@ImreSamu
Copy link
Contributor

ImreSamu commented Dec 3, 2023

According to the analysis of your log file, available at this link, there is a likelihood that your Docker postgis service has been compromised, possibly due to Kinsing Malware attacks. 😢

see in your log:

/tmp/kinsing is not b3039abf2ad5202f4a9363b418002351, actual 

For guidance on how to handle this situation and secure your Docker image,
please refer to the recommendations provided in this discussion:

@rranjangupta
Copy link
Author

Thanks a lot @ImreSamu

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants