Root privilege escalation via symlink-following package scripts
Published Jan 24, 2020 · Updated Sep 17, 2024
Symlink following in SUSE-packaged Mailman allows local users to gain root privileges or change arbitrary files to group mailman. The Mailman RPM post-install script runs explicit chown and chmod operations on package paths, following attacker-controlled symbolic links instead of applying fixed file attributes. Exploitation requires local access as wwwrun or membership in the mailman group and occurs during package installation or update; successful abuse grants root privileges or changes a chosen file's group.
Summary
What happened
Symlink following in SUSE-packaged Mailman allows local users to gain root privileges or change arbitrary files to group mailman. The Mailman RPM post-install script runs explicit chown and chmod operations on package paths, following attacker-controlled symbolic links instead of applying fixed file attributes. Exploitation requires local access as wwwrun or membership in the mailman group and occurs during package installation or update; successful abuse grants root privileges or changes a chosen file's group.
The record
- CVE
- CVE-2019-3693
- Published
- Jan 24, 2020
- Updated
- Sep 17, 2024
- Vendor
- OpenSUSE
- Product
- openSUSE Leap
- Classifications
- CWE-59
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 24, 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=mailman <=2.1.29-lp151.2.14
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