S4E just found a high-severity finding from top 10 tcp port service scan
PlatformPlansPartners
Resources
ToolsBlogDocs
Sign Up →
high·Misconfiguration·Updated Oct 8, 2024

Postgres Default Login Scanner

This scanner probes Postgres instances for default usernames and passwords, allowing attackers to gain full database access.

Est. Time~1 minutes
Scan TypeSingle Scan
Targetsdomain, ipv4, subdomain
CostFree
2.9k
Times Used
continuous scan runs
6.4k
Continuously Checked
assets under CS
10
Vulnerabilities Found
confirmed findings
References
Detail

PostgreSQL, often called Postgres, is a powerful open-source relational database management system known for its reliability, extensibility, and SQL compliance. It is used by developers, startups, and large enterprises to store and manage structured data for web applications, analytics, and transaction processing. Postgres is a core component in many tech stacks, supporting complex queries and high concurrency.

The vulnerability detected is the use of default login credentials, such as 'postgres' with password 'postgres', which are often left unchanged after installation. This oversight creates a critical security gap, as attackers can easily guess these credentials using automated tools or simple scripts.

Technically, the scanner attempts to authenticate to the Postgres server on port 5432 using common default usernames and passwords. It targets the pg_hba.conf authentication configuration, which if misconfigured, allows remote connections with default credentials. The scanner checks for successful login without requiring any prior knowledge.

If exploited, an attacker gains full read and write access to all databases, enabling data theft, modification, or deletion. They can also execute arbitrary SQL commands, potentially leading to privilege escalation or lateral movement within the network. This can result in severe data breaches, compliance violations, and reputational damage.

Solution Advice
  • Change default credentials immediately: set strong, unique passwords for all Postgres users.
  • Enforce password complexity policies and use password managers to generate secure passwords.
  • Restrict network access to Postgres using firewalls, allowing only trusted IP addresses.
  • Disable remote login for the default 'postgres' user if not needed, or use SSH tunneling.
  • Regularly audit user accounts and remove unused or default accounts.
  • Implement multi-factor authentication (MFA) for database access where possible.
  • Monitor authentication logs for repeated failed attempts and set up alerts.
  • Apply the principle of least privilege: grant only necessary permissions to each user.

Get AI-powered remediation steps tailored to your asset.

Try AI Solutions →

Check your infrastructure.
Right now.

11,000+ scanners. Free to start. No credit card required.