Local privilege escalation via installer directory junction
Published Oct 27, 2023 · Updated Sep 9, 2024
Insecure junction handling in HashiCorp Vagrant's Windows installer before 2.4.0 allows local users to write files without authorization. When a custom installation location uses an unprotected path, the installer follows an attacker-created directory junction and writes installation files to the junction target. A local low-privileged user must prepare the junction before installation; resulting writes are system-dependent and can enable privilege escalation.
Summary
What happened
Insecure junction handling in HashiCorp Vagrant's Windows installer before 2.4.0 allows local users to write files without authorization. When a custom installation location uses an unprotected path, the installer follows an attacker-created directory junction and writes installation files to the junction target. A local low-privileged user must prepare the junction before installation; resulting writes are system-dependent and can enable privilege escalation.
The record
- CVE
- CVE-2023-5834
- Published
- Oct 27, 2023
- Updated
- Sep 9, 2024
- Vendor
- HashiCorp
- Product
- Vagrant
- Classifications
- CWE-59, CWE-1386, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 27, 2023CVE publishedPublication date reported by the CVE source.
- Sep 9, 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=* <2.4.0
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