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.
References
Link | Resource |
---|---|
http://www.securityfocus.com/bid/102986 | Third Party Advisory VDB Entry |
https://access.redhat.com/errata/RHSA-2018:2511 | Third Party Advisory |
https://access.redhat.com/errata/RHSA-2018:2566 | Third Party Advisory |
https://access.redhat.com/errata/RHSA-2018:3816 | Third Party Advisory |
https://lists.debian.org/debian-lts-announce/2018/02/msg00006.html | Mailing List Third Party Advisory |
https://usn.ubuntu.com/3564-1/ | Third Party Advisory |
https://www.postgresql.org/about/news/1829/ | Patch Release Notes Third Party Advisory |
Configurations
Configuration 1 (hide)
|
Configuration 2 (hide)
|
Configuration 3 (hide)
|
Configuration 4 (hide)
|
History
No history.
Information
Published : 2018-02-09 14:29
Updated : 2024-02-28 16:25
NVD link : CVE-2018-1053
Mitre link : CVE-2018-1053
CVE.ORG link : CVE-2018-1053
JSON object : View
Products Affected
redhat
- cloudforms
canonical
- ubuntu_linux
debian
- debian_linux
postgresql
- postgresql