dbcve.org
Repository Mirroring ToolApplication · Suse

CVE-2018-17957

HIGH · 7.8 CVSS v3.0 Published 2018-12-26
Fix available
A fix is available. Upgrade to 1.1.2 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The YaST2 RMT module for SUSE Repository Mirroring Tool before version 1.1.2 exposed MySQL database passwords as command-line arguments when spawning processes. This made credentials visible through process inspection tools (e.g., ps), allowing local attackers to obtain database credentials and access or corrupt the RMT database.

MitigationUpgrade the YaST2 RMT module to version 1.1.2 or later, which addresses the command-line credential exposure. Verify that process listings no longer reveal database passwords.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Repository Mirroring ToolApplication
Affected:< 1.1.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify if RMT is installed
    Check for the presence of the YaST2 RMT module or SUSE Repository Mirroring Tool on the system using the package manager or by querying installed packages
    Affected if The RMT software is installed on the system
  2. Identify the installed RMT version
    Query the package manager for the version of the yast2-rmt or rmt-server package, or run the RMT version command if available
    Affected if The installed version is less than 1.1.2
  3. Inspect process command lines for database passwords
    While RMT is running database operations, use process inspection tools such as ps, top, or /proc filesystem to examine command-line arguments of RMT-related processes
    Affected if MySQL database passwords are visible in plain text within process command-line arguments

You are affected if RMT is installed with a version prior to 1.1.2 and database credentials are exposed in process command-line arguments

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to 1.1.2 or later
Fixed in 1.1.2
Interim mitigation

Upgrade the YaST2 RMT module to version 1.1.2 or later, which addresses the command-line credential exposure. Verify that process listings no longer reveal database passwords.

Fix this in Repository Mirroring Tool Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-17957 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-17957 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data