Root privilege escalation via package-upgrade symlink
Published Mar 2, 2020 · Updated Sep 17, 2024
Symlink following in Salt packaging for SLES 12, SLES 15, and openSUSE Factory allows local users to escalate from salt to root. During a salt-master package upgrade, privileged packaging operations follow a filesystem link controlled by the salt account instead of safely resolving the intended path. The attacker must already control the local salt service account and wait for or induce a privileged salt-master upgrade; successful exploitation grants root-level control.
Summary
What happened
Symlink following in Salt packaging for SLES 12, SLES 15, and openSUSE Factory allows local users to escalate from salt to root. During a salt-master package upgrade, privileged packaging operations follow a filesystem link controlled by the salt account instead of safely resolving the intended path. The attacker must already control the local salt service account and wait for or induce a privileged salt-master upgrade; successful exploitation grants root-level control.
The record
- CVE
- CVE-2019-18897
- Published
- Mar 2, 2020
- Updated
- Sep 17, 2024
- Vendor
- SUSE
- Product
- SUSE Linux Enterprise Server
- Classifications
- CWE-59, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 2, 2020CVE publishedPublication date reported by the CVE source.
- Sep 17, 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=salt-master <=2019.2.0-46.83.1
- Affected versionversion=salt-master <=2019.2.0-6.21.1
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