CVE-2018-1053

What it is

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.

At a glance

Exploitability

Can be exploited locally on the machine with a low-privilege account. High risk of data exposure, data tampering, service disruption.

Exploit odds

0.5% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2018-02-09 14:29 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 01:50 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.5% in the next 30 days (EPSS).
• Severity: 7.0 HIGH (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2018-02-09 14:29 UTC

Last modified

2026-06-17 01:50 UTC

Exploit probability

0.5% · EPSS, next 30 days

Weakness

CWE-377

Record status

Modified

Affected

• PostgreSQL < 9.3.21
• PostgreSQL < 9.4.16
• PostgreSQL < 9.5.11
• PostgreSQL < 9.6.7
• PostgreSQL 10.0
• PostgreSQL 10.1
• Debian Linux 7.0
• Canonical Ubuntu Linux 14.04

Attack profile CVSS 3.0 · 7.0

Attack vector

Local

Complexity

High

Privileges needed

Low

User interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2018-1053.md and follow it. Check whether this project is affected by CVE-2018-1053. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge