CA private-key passphrase disclosure via command logging
Published Jan 27, 2020 · Updated Sep 16, 2024
Sensitive-data logging in yast2-rmt before 1.2.2 allows local users to read the CA private-key passphrase on SLES 15 and openSUSE Leap. The YaST RMT module passes the SSL password to the Cheetah command-line interface in a form that command logging records in a log file. Exploitation requires local access to that log; the exposed passphrase can unlock the RMT custom CA private key, while no data modification or service interruption is reported.
Summary
What happened
Sensitive-data logging in yast2-rmt before 1.2.2 allows local users to read the CA private-key passphrase on SLES 15 and openSUSE Leap. The YaST RMT module passes the SSL password to the Cheetah command-line interface in a form that command logging records in a log file. Exploitation requires local access to that log; the exposed passphrase can unlock the RMT custom CA private key, while no data modification or service interruption is reported.
The record
- CVE
- CVE-2018-20105
- Published
- Jan 27, 2020
- Updated
- Sep 16, 2024
- Vendor
- OpenSUSE
- Product
- openSUSE Leap
- Classifications
- CWE-532, T1552.001
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Jan 27, 2020CVE publishedPublication date reported by the CVE source.
- Sep 16, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=yast2-rmt <1.2.2
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo