CVE-2018-1053

N/A
Published: February 9, 2018 at 02:00 PM UTC
Updated: June 17, 2026 at 01:50 AM UTC
5 products affected across 5 vendorsDebian LinuxUbuntu LinuxPostgreSQL

Using postgresql by The PostgreSQL Global Development Group?

Get instant alerts when new vulnerabilities affect postgresql - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.5%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

9.3.0 ≤ v < 9.3.219.4.0 ≤ v < 9.4.169.5.0 ≤ v < 9.5.119.6.0 ≤ v < 9.6.710.010.1
Affected range stops below 9.3.21, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.4.16, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.5.11, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.6.7, so it looks safe — our inference, not a vendor statement
10 ≤ v < 10.29.3 ≤ v < 9.3.219.4 ≤ v < 9.4.169.5 ≤ v < 9.5.119.6 ≤ v < 9.6.7
Affected range stops below 10.2, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.3.21, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.4.16, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.5.11, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.6.7, so it looks safe — our inference, not a vendor statement

References (7)

VDB Entryx_refsource_BIDThird Party Advisory
http://www.securityfocus.com/bid/102986
Vendor Advisoryx_refsource_REDHATThird Party Advisory
https://access.redhat.com/errata/RHSA-2018:2511
Vendor Advisoryx_refsource_REDHATThird Party Advisory
https://access.redhat.com/errata/RHSA-2018:2566
Vendor Advisoryx_refsource_REDHATThird Party Advisory
https://access.redhat.com/errata/RHSA-2018:3816
Mailing Listx_refsource_MLISTThird Party Advisory
https://lists.debian.org/debian-lts-announce/2018/02/msg00006.html
Vendor Advisoryx_refsource_UBUNTUThird Party Advisory
https://usn.ubuntu.com/3564-1/
x_refsource_CONFIRMPatchRelease NotesThird Party Advisory
https://www.postgresql.org/about/news/1829/

CVSS

Confidentiality
PARTIAL
Integrity
PARTIAL
Availability
NONE
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-377CWE-732

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card