Skip to main content

Over 150 LLM Providers · Over 5,300 Models The most extensible AI-powered pentesting platform. Open source. Star on GitHub

CVE-2018-1053

7.0 · HIGH
Published Feb 9, 2018 postgresql CWE-377 EPSS 0.48% (40th pctl)

Overview

CVE-2018-1053 is a high-severity vulnerability affecting postgresql postgresql. It was published on February 9, 2018 and has a CVSS 3.0 base score of 7.0 (HIGH).

This vulnerability has a CVSS 3.0 base score of 7.0, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical Description

In postgresql 9.3.x before 9.3.21, 9.4.x before 9.4.16, 9.5.x before 9.5.11, 9.6.x before 9.6.7 and 10.x before 10.2, pg_upgrade creates file in current working directory containing the output of `pg_dumpall -g` under umask which was in effect when the user invoked pg_upgrade, and not under 0077 which is normally used for other temporary files. This can allow an authenticated attacker to read or modify the one file, which may contain encrypted or unencrypted database passwords. The attack is infeasible if a directory mode blocks the attacker searching the current working directory or if the prevailing umask blocks the attacker opening the file.

Remediation

Check the references section for vendor advisories and patches from postgresql. Update postgresql to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Affected Products

Vendor Product Versions Status
postgresql postgresql >= 9.3.0, < 9.3.21 Affected

Frequently Asked Questions

What is CVE-2018-1053?

CVE-2018-1053 is a high-severity vulnerability affecting postgresql postgresql. It was published on February 9, 2018 and has a CVSS 3.0 base score of 7.0 (HIGH).

How severe is CVE-2018-1053?

This vulnerability has a CVSS 3.0 base score of 7.0, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2018-1053?

Check the references section for vendor advisories and patches from postgresql. Update postgresql to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2018-1053?

CyberStrike's AI-powered security agents can automatically detect CVE-2018-1053 across your infrastructure using autonomous pentesting, DAST scanning, and HackBrowser. The platform continuously monitors for known vulnerabilities and provides actionable remediation guidance prioritized by real-world exploitability.