CVE-2018-1053

Name: CVE-2018-1053
Creator: NVD / NIST
Published: 2018-02-09T14:29:00.26+00:00
License: https://creativecommons.org/publicdomain/zero/1.0/

UnknownEPSS 0.49%

Last modified Jun 17, 2026

CVE-2018-1053 is a vulnerability of currently unknown severity. 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. EPSS estimates a 0.49% chance of exploitation in the next 30 days.

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.

Metrics

EPSS Probability

0.49%

38.4th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

Vendor	Product	Versions
Postgresql	Postgresql	>= 9.3.0, < 9.3.21
Postgresql	Postgresql	>= 9.4.0, < 9.4.16
Postgresql	Postgresql	>= 9.5.0, < 9.5.11
Postgresql	Postgresql	>= 9.6.0, < 9.6.7
Postgresql	Postgresql	10.0
Postgresql	Postgresql	10.1
Debian	Debian Linux	7.0
Canonical	Ubuntu Linux	14.04
Canonical	Ubuntu Linux	16.04
Canonical	Ubuntu Linux	17.10
Redhat	Cloudforms	4.6

References

http://www.securityfocus.com/bid/102986Third Party Advisory, VDB Entry
https://access.redhat.com/errata/RHSA-2018:2511Third Party Advisory
https://access.redhat.com/errata/RHSA-2018:2566Third Party Advisory
https://access.redhat.com/errata/RHSA-2018:3816Third Party Advisory
https://lists.debian.org/debian-lts-announce/2018/02/msg00006.htmlMailing 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
http://www.securityfocus.com/bid/102986Third Party Advisory, VDB Entry
https://access.redhat.com/errata/RHSA-2018:2511Third Party Advisory
https://access.redhat.com/errata/RHSA-2018:2566Third Party Advisory
https://access.redhat.com/errata/RHSA-2018:3816Third Party Advisory
https://lists.debian.org/debian-lts-announce/2018/02/msg00006.htmlMailing 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

Timeline

Published: Feb 9, 2018
Last Modified: Jun 17, 2026
Status: Modified

Frequently Asked Questions

What is CVE-2018-1053?

How severe is CVE-2018-1053?

Severity scoring for CVE-2018-1053 is pending analysis. The EPSS model estimates a 0.49% probability of exploitation in the next 30 days.

How do I fix CVE-2018-1053?

Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2018-1053?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST