Skip to content
Noroxi
CVE-2018-1053· NVD / CVE Program· CNA redhat

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 fil

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.

HighCVSS 7.0 · v3.0—No exploit Fix available
Published
Feb 9, 2018
Updated
Jun 16, 2026
EPSS
0.5% · 39th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

28

Monitor

Low priority for now.

CVSS
28 / 40 · 7.0 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.5%

Affected systems

VendorProduct
postgresqlpostgresql
debiandebian linux
canonicalubuntu linux
redhatcloudforms

Using postgresql? Add it to your stack and be the first to know about CVEs like this one. (PostgreSQL)

Add to my stack

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • postgresql postgresql9.3.0 and later · before 9.3.21
  • postgresql postgresql9.4.0 and later · before 9.4.16
  • postgresql postgresql9.5.0 and later · before 9.5.11
  • postgresql postgresql9.6.0 and later · before 9.6.7
  • postgresql postgresql10.0
  • postgresql postgresql10.1

Versions reported by the vendor

Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.

  • The PostgreSQL Global Development Group 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, 10.x before 10.2affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Alpine:v3.10postgresqlfrom 9.3.0 · before 10.2-r010.2-r0
Alpine:v3.15postgresql14before 10.2-r010.2-r0
Alpine:v3.17postgresql15before 10.2-r010.2-r0
Alpine:v3.4postgresqlfrom 9.3.0 · before 9.5.11-r09.5.11-r0
Alpine:v3.5postgresqlfrom 9.3.0 · before 9.6.7-r09.6.7-r0
Debian:7postgresql-9.1before 9.1.24lts2-0+deb7u29.1.24lts2-0+deb7u2
openSUSE:Tumbleweedpostgresql10before 10.18-1.310.18-1.3
Red Hat:cloudforms_managementengine:5.9::el7cfmebefore 0:5.9.6.5-3.el7cf0:5.9.6.5-3.el7cf
Red Hat:cloudforms_managementengine:5.9::el7cfme-amazon-smartstatebefore 0:5.9.6.5-2.el7cf0:5.9.6.5-2.el7cf
Red Hat:cloudforms_managementengine:5.9::el7cfme-appliancebefore 0:5.9.6.5-1.el7cf0:5.9.6.5-1.el7cf
Red Hat:cloudforms_managementengine:5.9::el7cfme-appliance-commonbefore 0:5.9.6.5-1.el7cf0:5.9.6.5-1.el7cf
Red Hat:cloudforms_managementengine:5.9::el7cfme-appliance-debuginfobefore 0:5.9.6.5-1.el7cf0:5.9.6.5-1.el7cf
Red Hat:cloudforms_managementengine:5.9::el7cfme-appliance-toolsbefore 0:5.9.6.5-1.el7cf0:5.9.6.5-1.el7cf
Red Hat:cloudforms_managementengine:5.9::el7cfme-debuginfobefore 0:5.9.6.5-3.el7cf0:5.9.6.5-3.el7cf
Red Hat:cloudforms_managementengine:5.9::el7cfme-gemsetbefore 0:5.9.6.5-2.el7cf0:5.9.6.5-2.el7cf
Red Hat:cloudforms_managementengine:5.9::el7cfme-gemset-debuginfobefore 0:5.9.6.5-2.el7cf0:5.9.6.5-2.el7cf
Red Hat:cloudforms_managementengine:5.9::el7dbus-api-servicebefore 0:1.0.1-3.1.el7cf0:1.0.1-3.1.el7cf
Red Hat:cloudforms_managementengine:5.9::el7httpd-configmap-generatorbefore 0:0.2.2-1.2.el7cf0:0.2.2-1.2.el7cf
Red Hat:cloudforms_managementengine:5.9::el7postgresql96before 0:9.6.10-1PGDG.el7at0:9.6.10-1PGDG.el7at
Red Hat:cloudforms_managementengine:5.9::el7postgresql96-contribbefore 0:9.6.10-1PGDG.el7at0:9.6.10-1PGDG.el7at
Red Hat:cloudforms_managementengine:5.9::el7postgresql96-debuginfobefore 0:9.6.10-1PGDG.el7at0:9.6.10-1PGDG.el7at
Red Hat:cloudforms_managementengine:5.9::el7postgresql96-develbefore 0:9.6.10-1PGDG.el7at0:9.6.10-1PGDG.el7at
Red Hat:cloudforms_managementengine:5.9::el7postgresql96-docsbefore 0:9.6.10-1PGDG.el7at0:9.6.10-1PGDG.el7at
Red Hat:cloudforms_managementengine:5.9::el7postgresql96-libsbefore 0:9.6.10-1PGDG.el7at0:9.6.10-1PGDG.el7at

+65

Other highest-scoring records for the same primary product.

  • CVE-2017-7546PostgreSQL versions before 9.2.22, 9.3.18, 9.4.13, 9.5.8 and 9.6.4 are vulnerable to incorrect authentication flaw allowing remote attackers
    57Plan
  • CVE-2019-9193In PostgreSQL 9.3 through 11.2, the "COPY TO/FROM PROGRAM" function allows superusers and users in the 'pg_execute_server_program' group to
    55Plan
  • CVE-2020-25695A flaw was found in PostgreSQL versions before 13.1, before 12.5, before 11.10, before 10.15, before 9.6.20 and before 9.5.24.
    49Plan
  • CVE-2007-3280The Database Link library (dblink) in PostgreSQL 8.1 implements functions via CREATE statements that map to arbitrary libraries based on the
    44Plan
  • CVE-2013-1899Argument injection vulnerability in PostgreSQL 9.2.x before 9.2.4, 9.1.x before 9.1.9, and 9.0.x before 9.0.13 allows remote attackers to ca
    42Plan
  • CVE-2018-16850postgresql before versions 11.1, 10.6 is vulnerable to a to SQL injection in pg_upgrade and pg_dump via CREATE TRIGGER ...
    41Plan

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Alpine:postgresql10.2-r0 · Alpine:v3.10Package registry (OSV)
Alpine:postgresql1410.2-r0 · Alpine:v3.15Package registry (OSV)
Alpine:postgresql1510.2-r0 · Alpine:v3.17Package registry (OSV)
Debian:postgresql-9.19.1.24lts2-0+deb7u2 · Debian:7Package registry (OSV)
openSUSE:postgresql1010.18-1.3 · openSUSE:TumbleweedPackage registry (OSV)
Red Hat:rh-postgresql95-postgresql0:9.5.14-1.el6 · Red Hat:rhel_software_collections:3::el6Package registry (OSV)
Red Hat:rh-postgresql95-postgresql-contrib0:9.5.14-1.el6 · Red Hat:rhel_software_collections:3::el6Package registry (OSV)
Red Hat:rh-postgresql95-postgresql-debuginfo0:9.5.14-1.el6 · Red Hat:rhel_software_collections:3::el6Package registry (OSV)
Red Hat:rh-postgresql95-postgresql-devel0:9.5.14-1.el6 · Red Hat:rhel_software_collections:3::el6Package registry (OSV)
Red Hat:rh-postgresql95-postgresql-docs0:9.5.14-1.el6 · Red Hat:rhel_software_collections:3::el6Package registry (OSV)
Red Hat:rh-postgresql95-postgresql-libs0:9.5.14-1.el6 · Red Hat:rhel_software_collections:3::el6Package registry (OSV)
Red Hat:rh-postgresql95-postgresql-plperl0:9.5.14-1.el6 · Red Hat:rhel_software_collections:3::el6Package registry (OSV)
Red Hat:rh-postgresql95-postgresql-plpython0:9.5.14-1.el6 · Red Hat:rhel_software_collections:3::el6Package registry (OSV)
Red Hat:rh-postgresql95-postgresql-pltcl0:9.5.14-1.el6 · Red Hat:rhel_software_collections:3::el6Package registry (OSV)
Red Hat:rh-postgresql95-postgresql-server0:9.5.14-1.el6 · Red Hat:rhel_software_collections:3::el6Package registry (OSV)
Red Hat:rh-postgresql95-postgresql-static0:9.5.14-1.el6 · Red Hat:rhel_software_collections:3::el6Package registry (OSV)
Red Hat:rh-postgresql95-postgresql-test0:9.5.14-1.el6 · Red Hat:rhel_software_collections:3::el6Package registry (OSV)
SUSE:postgresql949.4.16-0.23.13.2 · SUSE:Linux Enterprise Server 11 SP4Package registry (OSV)
SUSE:postgresql94-libs9.4.16-0.23.13.2 · SUSE:Linux Enterprise Software Development Kit 11 SP4Package registry (OSV)
SUSE:postgresql969.6.7-3.13.1 · SUSE:Linux Enterprise Desktop 12 SP2Package registry (OSV)
SUSE:postgresql96-libs9.6.7-3.13.1 · SUSE:Linux Enterprise Desktop 12 SP2Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
High
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

CVSS vector

CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records