# CVE-2018-1053: Information disclosure in postgresql

> An authenticated attacker can read or modify a temporary file containing database passwords due to improper file permissions during pg_upgrade execution.

- **Severity:** High 7.0 (`CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Feb 2018
- **Updated:** 17 Sep 2024
- **Also known as:** ALPINE-CVE-2018-1053, CLEANSTART-2026-ZK79671, DLA-1271-1, GHSA-h73g-3m4r-j2cr, MGASA-2018-0137, SUSE-SU-2018:0506-1, SUSE-SU-2018:0507-1, SUSE-SU-2018:0675-1, UBUNTU-CVE-2018-1053, USN-3564-1

## What is CVE-2018-1053?

CVE-2018-1053 is a high-severity vulnerability in Canonical Ubuntu Linux, published on 9 Feb 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource), CWE-377 (DEPRECATED: Insecure Temporary File)

## Which versions are affected by CVE-2018-1053?

It affects 4 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `postgresql94` | SUSE:Linux Enterprise Desktop 12 SP2 | All versions | 9.4.16-21.16.1 |
| `postgresql96` | SUSE:Linux Enterprise Desktop 12 SP2 | All versions | 9.6.7-3.13.1 |
| `postgresql96-libs` | SUSE:Linux Enterprise Desktop 12 SP2 | All versions | 9.6.7-3.13.1 |
| `postgresql96` | SUSE:Linux Enterprise Desktop 12 SP3 | All versions | 9.6.7-3.13.1 |
| `postgresql96-libs` | SUSE:Linux Enterprise Desktop 12 SP3 | All versions | 9.6.7-3.13.1 |
| `postgresql94` | SUSE:Linux Enterprise Server 11 SP4 | All versions | 9.4.16-0.23.13.2 |
| `postgresql94-libs` | SUSE:Linux Enterprise Server 11 SP4 | All versions | 9.4.16-0.23.13.2 |
| `postgresql94` | SUSE:Linux Enterprise Server 12 SP2 | All versions | 9.4.16-21.16.1 |
| `postgresql96` | SUSE:Linux Enterprise Server 12 SP2 | All versions | 9.6.7-3.13.1 |
| `postgresql96-libs` | SUSE:Linux Enterprise Server 12 SP2 | All versions | 9.6.7-3.13.1 |
| `postgresql96` | SUSE:Linux Enterprise Server 12 SP3 | All versions | 9.6.7-3.13.1 |
| `postgresql96-libs` | SUSE:Linux Enterprise Server 12 SP3 | All versions | 9.6.7-3.13.1 |
| `postgresql94` | SUSE:Linux Enterprise Server for Raspberry Pi 12 SP2 | All versions | 9.4.16-21.16.1 |
| `postgresql96` | SUSE:Linux Enterprise Server for Raspberry Pi 12 SP2 | All versions | 9.6.7-3.13.1 |
| `postgresql96-libs` | SUSE:Linux Enterprise Server for Raspberry Pi 12 SP2 | All versions | 9.6.7-3.13.1 |
| `postgresql94` | SUSE:Linux Enterprise Server for SAP Applications 11 SP4 | All versions | 9.4.16-0.23.13.2 |
| `postgresql94-libs` | SUSE:Linux Enterprise Server for SAP Applications 11 SP4 | All versions | 9.4.16-0.23.13.2 |
| `postgresql94` | SUSE:Linux Enterprise Server for SAP Applications 12 SP2 | All versions | 9.4.16-21.16.1 |
| `postgresql96` | SUSE:Linux Enterprise Server for SAP Applications 12 SP2 | All versions | 9.6.7-3.13.1 |
| `postgresql96-libs` | SUSE:Linux Enterprise Server for SAP Applications 12 SP2 | All versions | 9.6.7-3.13.1 |
| `postgresql96` | SUSE:Linux Enterprise Server for SAP Applications 12 SP3 | All versions | 9.6.7-3.13.1 |
| `postgresql96-libs` | SUSE:Linux Enterprise Server for SAP Applications 12 SP3 | All versions | 9.6.7-3.13.1 |
| `postgresql94-libs` | SUSE:Linux Enterprise Software Development Kit 11 SP4 | All versions | 9.4.16-0.23.13.2 |
| `postgresql94-libs` | SUSE:Linux Enterprise Software Development Kit 12 SP2 | All versions | 9.4.16-21.16.1 |
| `postgresql96-libs` | SUSE:Linux Enterprise Software Development Kit 12 SP2 | All versions | 9.6.7-3.13.1 |
| `postgresql96-libs` | SUSE:Linux Enterprise Software Development Kit 12 SP3 | All versions | 9.6.7-3.13.1 |

Products: Canonical Ubuntu Linux, Debian Debian Linux, Postgresql Postgresql, Redhat Cloudforms.

## How do I fix CVE-2018-1053?

Upgrade to a fixed version.

## Is CVE-2018-1053 being exploited?

There is no known exploitation of CVE-2018-1053 in the wild and no public exploit code.

## Other vulnerabilities in Canonical Ubuntu Linux

- [CVE-2020-11651](https://insights.sbomify.com/CVE-2020-11651/): SaltStack Salt Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2020-7247](https://insights.sbomify.com/CVE-2020-7247/): OpenSMTPD Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2019-16928](https://insights.sbomify.com/CVE-2019-16928/): Exim Out-of-bounds Write (critical 9.8, exploited in the wild)
- [CVE-2018-6789](https://insights.sbomify.com/CVE-2018-6789/): Exim Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2015-2590](https://insights.sbomify.com/CVE-2015-2590/): Oracle Java SE and Java SE Embedded Remote Code Execution (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-1053 and fix it if it is affected.

What it is: CVE-2018-1053 is a high-severity vulnerability in Canonical Ubuntu Linux, published on 9 Feb 2018. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-1053 in the wild and no public exploit code.

Affected product: Canonical Ubuntu Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-1053/ (Markdown: https://insights.sbomify.com/CVE-2018-1053/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-1053
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-1053
- OSV: https://osv.dev/vulnerability/CVE-2018-1053

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-1053/
Summaries are generated and may contain mistakes; the official description above is the record.