System privilege escalation via replaceable service binary
Published Jun 13, 2024 · Updated Aug 2, 2024
Privilege escalation in DNSCrypt dnscrypt-proxy 2.0.0alpha9 through 2.1.5 allows local users to execute code as root or LocalSystem. The service-install path leaves the registered dnscrypt-proxy executable replaceable by nonprivileged users, so the service launches substituted code with its elevated account. Exploitation requires a service installation, local write access to the binary or its directory, and a later service restart such as a reboot.
Summary
What happened
Privilege escalation in DNSCrypt dnscrypt-proxy 2.0.0alpha9 through 2.1.5 allows local users to execute code as root or LocalSystem. The service-install path leaves the registered dnscrypt-proxy executable replaceable by nonprivileged users, so the service launches substituted code with its elevated account. Exploitation requires a service installation, local write access to the binary or its directory, and a later service restart such as a reboot.
The record
- CVE
- CVE-2024-36587
- Published
- Jun 13, 2024
- Updated
- Aug 2, 2024
- Vendor
- DNSCrypt
- Product
- dnscrypt-proxy
- Classifications
- CWE-266, T1574.010
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 13, 2024CVE publishedPublication date reported by the CVE source.
- Aug 2, 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=v2.0.0alpha9 <=v2.1.5
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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