# CVE-2018-17957: yast2-rmt leaks database passwords in process list

> Local attackers can read MySQL passwords from process lists to access or corrupt the SUSE Repository Mirroring Tool database.

- **Severity:** Low 3.4 (`CVSS:3.0/AV:L/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Dec 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-hr76-mvvj-82f3, SUSE-SU-2018:4209-1

## What is CVE-2018-17957?

CVE-2018-17957 is a low-severity vulnerability in SUSE yast2-rmt, published on 26 Dec 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The YaST2 RMT module for configuring the SUSE Repository Mirroring Tool (RMT) before 1.1.2 exposed MySQL database passwords on process commandline, allowing local attackers to access or corrupt the RMT database.

Weakness: CWE-287 (Improper Authentication), CWE-214 (Invocation of Process Using Visible Sensitive Information)

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `yast2-rmt` | SUSE:Linux Enterprise Module for Server Applications 15 | All versions | 1.1.2-3.11.1 |

Products: Suse Repository Mirroring Tool.

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

Upgrade to a fixed version.

## Is CVE-2018-17957 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-17957 is a low-severity vulnerability in SUSE yast2-rmt, published on 26 Dec 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-17957 in the wild and no public exploit code.

Affected product: SUSE yast2-rmt. 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-17957/ (Markdown: https://insights.sbomify.com/CVE-2018-17957/index.md)
```

## Sources

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

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