VDB

CVE-2018-1053

CVE-2018-1053 PUBLISHED

Reported by redhat · Published February 9, 2018

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

VendorProductVersions
The PostgreSQL Global Development Grouppostgresql9.3.x before 9.3.21, 9.4.x before 9.4.16, 9.5.x before 9.5.11
The PostgreSQL Global Development Grouppostgresql9.3.x, 9.4.x, 9.5.x
alpinepostgresql0, 0, 0
alpinepostgresql150
alpinepostgresql140

Timeline

  • Feb 7, 2018 CVE Published
  • Apr 14, 2021 EPSS Score (30 in total, the first dated here)
  • Oct 10, 2025 CVE Updated
  • Mar 6, 2026 Distribution Patch (4 in total, the first dated here)
  • Mar 6, 2026 Security Advisory (5 in total, the first dated here)
  • Sep 26, 2026 Coalition ESS Score

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2018-1053
vulnetix vdb fixes CVE-2018-1053

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2018-1053/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

References

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›