Privilege escalation via root symlink writes
Published Jan 23, 2020 · Updated Sep 17, 2024
Improper privilege management in openSUSE Leap 15.1 apt-cacher-ng before 3.1-lp151.3.3.1 allows local users to write privileged files. The openSUSE systemd unit runs the daemon as root while /run/apt-cacher-ng remains owned by the unprivileged apt-cacher-ng account, so attacker-created symlinks redirect root writes. Control of that local service account and a service restart are required; replacing its Unix socket can also hijack privileged client connections.
Summary
What happened
Improper privilege management in openSUSE Leap 15.1 apt-cacher-ng before 3.1-lp151.3.3.1 allows local users to write privileged files. The openSUSE systemd unit runs the daemon as root while /run/apt-cacher-ng remains owned by the unprivileged apt-cacher-ng account, so attacker-created symlinks redirect root writes. Control of that local service account and a service restart are required; replacing its Unix socket can also hijack privileged client connections.
The record
- CVE
- CVE-2019-18899
- Published
- Jan 23, 2020
- Updated
- Sep 17, 2024
- Vendor
- OpenSUSE
- Product
- openSUSE Leap
- Classifications
- CWE-269, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 23, 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=apt-cacher-ng <3.1-lp151.3.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
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