Local privilege escalation via ls-R symlink race
Published Apr 2, 2020 · Updated Sep 16, 2024
Link-following race in texlive-filesystem on affected SUSE and openSUSE releases allows local users to corrupt privileged files. The root-run RPM post-install script creates and changes ownership and mode of ls-R files inside group-writable, sticky directories without preventing symlink replacement. A local user able to write as nobody or through the mktex group can win the race during package installation and redirect those operations to a system file, enabling privilege escalation.
Summary
What happened
Link-following race in texlive-filesystem on affected SUSE and openSUSE releases allows local users to corrupt privileged files. The root-run RPM post-install script creates and changes ownership and mode of ls-R files inside group-writable, sticky directories without preventing symlink replacement. A local user able to write as nobody or through the mktex group can win the race during package installation and redirect those operations to a system file, enabling privilege escalation.
The record
- CVE
- CVE-2020-8016
- Published
- Apr 2, 2020
- Updated
- Sep 16, 2024
- Vendor
- OpenSUSE
- Product
- openSUSE Leap
- Classifications
- CWE-367, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 2, 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=texlive-filesystem <2017.135-lp151.8.3.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
- inotify ls-R symlink race proof of conceptproof of concept · demonstrated
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