CVE-2018-1053 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_d...
HighCVSS 7.0
EPSS 0.48%
- Published
- Updated
- Exploit status
- No public exploit known
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
| Product | Affected versions | Fixed in |
|---|---|---|
| postgresql | >= 9.3.0, < 9.3.21 | 9.3.21 |
| postgresql | >= 9.4.0, < 9.4.16 | 9.4.16 |
| postgresql | >= 9.5.0, < 9.5.11 | 9.5.11 |
| postgresql | >= 9.6.0, < 9.6.7 | 9.6.7 |
| postgresql | = 10.0 | No fix listed |
| postgresql | = 10.1 | No fix listed |
| debian linux | = 7.0 | No fix listed |
| Canonical Ubuntu Linux | = 14.04 | No fix listed |
| Canonical Ubuntu Linux | = 16.04 | No fix listed |
| Canonical Ubuntu Linux | = 17.10 | No fix listed |
| redhat cloudforms | = 4.6 | No fix listed |
| The PostgreSQL Global Development Group PostgreSQL | = 9.3.x before 9.3.21 | No fix listed |
| The PostgreSQL Global Development Group PostgreSQL | = 9.4.x before 9.4.16 | No fix listed |
| The PostgreSQL Global Development Group PostgreSQL | = 9.5.x before 9.5.11 | No fix listed |
| The PostgreSQL Global Development Group PostgreSQL | = 9.6.x before 9.6.7 | No fix listed |
| The PostgreSQL Global Development Group PostgreSQL | = 10.x before 10.2 | No fix listed |
| alpine/postgresql(Alpine:v3.10) | >= 9.6.0, < 10.2-r0 | 10.2-r0 |
| alpine/postgresql(Alpine:v3.11) | >= 9.6.0, < 10.2-r0 | 10.2-r0 |
| alpine/postgresql(Alpine:v3.12) | >= 9.6.0, < 10.2-r0 | 10.2-r0 |
| alpine/postgresql(Alpine:v3.13) | >= 9.6.0, < 10.2-r0 | 10.2-r0 |
| alpine/postgresql(Alpine:v3.14) | >= 9.6.0, < 10.2-r0 | 10.2-r0 |
| alpine/postgresql(Alpine:v3.4) | >= 9.5.0, < 9.5.11-r0 | 9.5.11-r0 |
| alpine/postgresql(Alpine:v3.5) | >= 9.6.0, < 9.6.7-r0 | 9.6.7-r0 |
| alpine/postgresql(Alpine:v3.6) | >= 9.6.0, < 9.6.7-r0 | 9.6.7-r0 |
| alpine/postgresql(Alpine:v3.7) | >= 9.6.0, < 10.2-r0 | 10.2-r0 |
Show 12 more
| Product | Affected versions | Fixed in |
|---|---|---|
| alpine/postgresql(Alpine:v3.8) | >= 9.6.0, < 10.2-r0 | 10.2-r0 |
| alpine/postgresql(Alpine:v3.9) | >= 9.6.0, < 10.2-r0 | 10.2-r0 |
| alpine/postgresql14(Alpine:v3.15) | < 10.2-r0 | 10.2-r0 |
| alpine/postgresql14(Alpine:v3.16) | < 10.2-r0 | 10.2-r0 |
| alpine/postgresql14(Alpine:v3.17) | < 10.2-r0 | 10.2-r0 |
| alpine/postgresql14(Alpine:v3.18) | < 10.2-r0 | 10.2-r0 |
| alpine/postgresql14(Alpine:v3.19) | < 10.2-r0 | 10.2-r0 |
| alpine/postgresql14(Alpine:v3.20) | < 10.2-r0 | 10.2-r0 |
| alpine/postgresql15(Alpine:v3.17) | < 10.2-r0 | 10.2-r0 |
| alpine/postgresql15(Alpine:v3.18) | < 10.2-r0 | 10.2-r0 |
| alpine/postgresql15(Alpine:v3.19) | < 10.2-r0 | 10.2-r0 |
| alpine/postgresql15(Alpine:v3.20) | < 10.2-r0 | 10.2-r0 |
References
- 102986 third-party-advisory vdb-entry
- RHSA-2018:2511 third-party-advisory vendor-advisory
- RHSA-2018:2566 third-party-advisory vendor-advisory
- RHSA-2018:3816 third-party-advisory vendor-advisory
- [debian-lts-announce] 20180207 [SECURITY] [DLA-1271-1] postgresql-9.1 security update mailing-list third-party-advisory
- USN-3564-1 third-party-advisory vendor-advisory
- www.postgresql.org patch release-notes third-party-advisory
- security.alpinelinux.org vendor-advisory