CVE-2018-1053

Severity: high (CVSS 7.0 v3.0)
Exploited in the wild: not listed in CISA KEV
EPSS: 0.5% probability of exploitation in the next 30 days
Public exploit or detection template: none known
Published: 2018-02-09 · updated 2026-06-17
Weakness: CWE-377

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.

Affected products

Canonical Ubuntu Linux: 14.04, 16.04, 17.10
Debian Linux: 7.0
PostgreSQL: from 9.3.0 before 9.3.21; from 9.4.0 before 9.4.16; from 9.5.0 before 9.5.11; from 9.6.0 before 9.6.7; 10.0, 10.1 — fixed in 9.3.21, 9.4.16, 9.5.11, 9.6.7
CloudForms: 4.6

How to fix

Upgrade to a fixed version: PostgreSQL 9.3.21, 9.4.16, 9.5.11, 9.6.7. Check the vendor advisory for mitigations.

References

Get alerted when CVE-2018-1053 or the next vulnerability affects your stack