VDB
GCVE-110-MAGEIA-2018-137
GCVE-110-MAGEIA-2018-137
Advisory Published
In postgresql 9.4.x before 9.4.16 and 9.6.x before 9.6.7, 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 (CVE-2018-1053).
Note that on Mageia 5, only the postgresql9.4 update is being provided. Users
of the postgresql9.3 package should migrate to 9.4.
Affected Products
| Vendor | Product | Versions | Platforms |
|---|---|---|---|
| Mageia | lutris | 0.4.18-1.mga6 (unaffected), 0 (affected) | — |
| Mageia | postgresql9.4 | 0 (affected), 9.4.16-1.mga6 (unaffected), 0 (affected), 9.4.16-1.mga6 (unaffected) | — |
| Mageia | postgresql9.6 | 0 (affected), 9.6.7-1.mga6 (unaffected), 0 (affected), 9.6.7-1.mga6 (unaffected) | — |
| Mageia | postgresql9.4 | 0 (affected), 9.4.16-1.mga5 (unaffected), 9.4.16-1.mga5 (unaffected), 0 (affected) | — |
Aliases
References
Browse GCVE Records
73,040 records in the GCVE database · Updated July 15, 2026
No matching records found.
Explore Further
Investigate this vulnerability in the interactive console or download the raw GCVE record.