Root escalation via packaging symlink following
Published Jan 24, 2020 · Updated Sep 16, 2024
Symlink following in the Privoxy package for openSUSE Leap 15.1 and Factory allows local users to escalate from privoxy to root. Public SUSE and NVD records do not identify the affected packaging script, filesystem path, or privileged file operation that follows the link. Exploitation requires local access as the privoxy service account and grants root-level control over the host.
Summary
What happened
Symlink following in the Privoxy package for openSUSE Leap 15.1 and Factory allows local users to escalate from privoxy to root. Public SUSE and NVD records do not identify the affected packaging script, filesystem path, or privileged file operation that follows the link. Exploitation requires local access as the privoxy service account and grants root-level control over the host.
The record
- CVE
- CVE-2019-3699
- Published
- Jan 24, 2020
- Updated
- Sep 16, 2024
- Vendor
- OpenSUSE
- Product
- openSUSE Leap
- Classifications
- CWE-59, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 24, 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=privoxy <=3.0.28-lp151.1.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