CVE-2018-1053
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.
How to fix
- postgresql postgresql9.3.21, 9.4.16, 9.5.11, 9.6.7 or later
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| postgresql postgresql | 9.3.0 ≤ v < 9.3.21, 9.4.0 ≤ v < 9.4.16, 9.5.0 ≤ v < 9.5.11, 9.6.0 ≤ v < 9.6.7, 10.0, 10.1 | 9.3.21, 9.4.16, 9.5.11, 9.6.7 |
| debian debian_linux | 7.0 | — |
| canonical ubuntu_linux | 14.04, 16.04, 17.10 | — |
| redhat cloudforms | 4.6 | — |
Check your version
Choose the product and enter the version you run to see whether it falls in the affected range.
Attack Surface Management
See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.