postgresql postgresql CVE-2018-1053 vulnerability in PostgreSQL and Other Products
Published on February 9, 2018

product logo product logo product logo product logo
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.

Vendor Advisory Vendor Advisory Vendor Advisory Vendor Advisory NVD

Weakness Type

Insecure Temporary File

Creating and using insecure temporary files can leave application and system data vulnerable to attack.


Products Associated with CVE-2018-1053

You can be notified by email with stack.watch whenever vulnerabilities like CVE-2018-1053 are published in these products:

 
 
 
 

Affected Versions

The PostgreSQL Global Development Group postgresql:

Exploit Probability

EPSS
0.10%
Percentile
26.37%

EPSS (Exploit Prediction Scoring System) scores estimate the probability that a vulnerability will be exploited in the wild within the next 30 days. The percentile shows you how this score compares to all other vulnerabilities.