Vulnerabilities · 2018 · Postgresql
CVE-2018-1053
Postgresql vulnerability
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
Postgresql, Debian Linux, Ubuntu Linux, Cloudforms. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Postgresql runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- www.postgresql.org/about/news/1829/ · Patch
- www.securityfocus.com/bid/102986 · Third Party Advisory
- access.redhat.com/errata/RHSA-2018:2511 · Third Party Advisory
- access.redhat.com/errata/RHSA-2018:2566 · Third Party Advisory
- access.redhat.com/errata/RHSA-2018:3816 · Third Party Advisory
- lists.debian.org/debian-lts-announce/2018/02/msg00006.html · Third Party Advisory
- usn.ubuntu.com/3564-1/ · Third Party Advisory
- nvd.nist.gov/vuln/detail/CVE-2018-1053
- cve.org/CVERecord?id=CVE-2018-1053
More vulnerabilities in Postgresql products
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.