Root privilege escalation via writable mock-install directory
Published Jan 20, 2020 · Updated Aug 5, 2024
A race condition in Gentoo Portage 2.3.84 and earlier allows local users controlling the nagios account to gain root via package builds. During a nagios-core build, emake leaves the mock-image plugin directory owned by nagios until fowners changes ownership, allowing planted content to enter the live filesystem. Exploitation requires local nagios-account access and a concurrent privileged package build.
Summary
What happened
A race condition in Gentoo Portage 2.3.84 and earlier allows local users controlling the nagios account to gain root via package builds. During a nagios-core build, emake leaves the mock-image plugin directory owned by nagios until fowners changes ownership, allowing planted content to enter the live filesystem. Exploitation requires local nagios-account access and a concurrent privileged package build.
The record
- CVE
- CVE-2019-20384
- Published
- Jan 20, 2020
- Updated
- Aug 5, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-362, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 20, 2020CVE publishedPublication date reported by the CVE source.
- Aug 5, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- Portage insecure temporary location demonstrationproof 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