# CVE-2018-20105: yast2-rmt exposes CA private key passhrase in log-file

> Local attackers can read the CA private key passphrase from log files in yast2-rmt, compromising certificate security.

- **Severity:** Medium 4.0 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Jan 2020
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-j4cc-p6fj-6598, SUSE-SU-2019:0629-1, SUSE-SU-2020:0578-1, openSUSE-SU-2019:1089-1, openSUSE-SU-2020:0253-1, openSUSE-SU-2020:0320-1

## What is CVE-2018-20105?

CVE-2018-20105 is a medium-severity vulnerability in Opensuse Leap, published on 27 Jan 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A Inclusion of Sensitive Information in Log Files vulnerability in yast2-rmt of SUSE Linux Enterprise Server 15; openSUSE Leap allows local attackers to learn the password if they can access the log file. This issue affects: SUSE Linux Enterprise Server 15 yast2-rmt versions prior to 1.2.2. openSUSE Leap yast2-rmt versions prior to 1.2.2.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

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

It affects 3 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `yast2-rmt` | SUSE:Linux Enterprise Module for Server Applications 15 | All versions | 1.2.2-3.18.1 |
| `yast2-rmt` | SUSE:Linux Enterprise Module for Server Applications 15 SP1 | All versions | 1.3.0-3.5.1 |
| `yast2-rmt` | openSUSE:Leap 15.0 | All versions | 1.2.2-lp150.2.19.1 |
| `yast2-rmt` | openSUSE:Leap 15.1 | All versions | 1.2.2-lp151.2.3.1 |
| `yast2-rmt` | openSUSE:Leap 15.1 | All versions | 1.3.0-lp151.2.6.1 |

Products: Opensuse Leap, Suse Suse Linux Enterprise Server, Yast2-Rmt Project Yast2-Rmt.

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

Upgrade to a fixed version.

## Is CVE-2018-20105 being exploited?

There is no known exploitation of CVE-2018-20105 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-20105 and fix it if it is affected.

What it is: CVE-2018-20105 is a medium-severity vulnerability in Opensuse Leap, published on 27 Jan 2020. 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-20105 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-20105/ (Markdown: https://insights.sbomify.com/CVE-2018-20105/index.md)
```

## Sources

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

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