# CVE-2018-1115: Missing authorization in postgresql

> An attacker with database access can bypass ACLs in the adminpack extension to force log rotation, potentially causing denial of service.

- **Severity:** Medium 4.2 (`CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 May 2018
- **Updated:** 8 Oct 2026
- **Also known as:** ALPINE-CVE-2018-1115, CLEANSTART-2026-SF26103, GHSA-54w7-jv4g-qhqg, SUSE-SU-2018:1695-1, UBUNTU-CVE-2018-1115

## What is CVE-2018-1115?

CVE-2018-1115 is a medium-severity missing authorization vulnerability in Opensuse Leap, published on 10 May 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

postgresql before versions 10.4, 9.6.9 is vulnerable in the adminpack extension, the pg_catalog.pg_logfile_rotate() function doesn't follow the same ACLs than pg_rorate_logfile. If the adminpack is added to a database, an attacker able to connect to it could exploit this to force log rotation.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

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

It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `postgresql96` | SUSE:Linux Enterprise Desktop 12 SP3 | All versions | 9.6.9-3.19.1 |
| `postgresql96-libs` | SUSE:Linux Enterprise Desktop 12 SP3 | All versions | 9.6.9-3.19.1 |
| `postgresql96` | SUSE:Linux Enterprise Server 12 SP3 | All versions | 9.6.9-3.19.1 |
| `postgresql96-libs` | SUSE:Linux Enterprise Server 12 SP3 | All versions | 9.6.9-3.19.1 |
| `postgresql96` | SUSE:Linux Enterprise Server for SAP Applications 12 SP3 | All versions | 9.6.9-3.19.1 |
| `postgresql96-libs` | SUSE:Linux Enterprise Server for SAP Applications 12 SP3 | All versions | 9.6.9-3.19.1 |
| `postgresql96-libs` | SUSE:Linux Enterprise Software Development Kit 12 SP3 | All versions | 9.6.9-3.19.1 |

Products: Opensuse Leap, Postgresql Postgresql.

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

Upgrade to a fixed version.

## Is CVE-2018-1115 being exploited?

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

## Other vulnerabilities in Opensuse Leap

- [CVE-2015-4902](https://insights.sbomify.com/CVE-2015-4902/): Oracle Java SE Integrity Check (medium 5.3, exploited in the wild)
- [CVE-2017-14804](https://insights.sbomify.com/CVE-2017-14804/): package builds could use directory traversal to write outside of target area (critical 9.9)
- [CVE-2019-20787](https://insights.sbomify.com/CVE-2019-20787/): Teeworlds before 0.7.4 has an integer overflow when computing a tilemap size. (critical 9.8)
- [CVE-2019-8341](https://insights.sbomify.com/CVE-2019-8341/): Code injection in n/a (critical 9.8)
- [CVE-2019-6438](https://insights.sbomify.com/CVE-2019-6438/): Other in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-1115 is a medium-severity missing authorization vulnerability in Opensuse Leap, published on 10 May 2018. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-1115 in the wild and no public exploit code.

Affected product: Opensuse Leap. 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-1115/ (Markdown: https://insights.sbomify.com/CVE-2018-1115/index.md)
```

## Sources

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

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