Local code execution via insecure environment variable
Published Sep 3, 2024 · Updated Sep 5, 2024
Improper input validation in VMware Fusion 13.x before 13.6 allows local users to execute code through an insecure environment variable. VMware has not disclosed the variable, the component that consumes it, or how its value reaches executable code. Standard user privileges on the macOS host are required, and successful exploitation runs code in the context of the Fusion application.
Summary
What happened
Improper input validation in VMware Fusion 13.x before 13.6 allows local users to execute code through an insecure environment variable. VMware has not disclosed the variable, the component that consumes it, or how its value reaches executable code. Standard user privileges on the macOS host are required, and successful exploitation runs code in the context of the Fusion application.
The record
- CVE
- CVE-2024-38811
- Published
- Sep 3, 2024
- Updated
- Sep 5, 2024
- Vendor
- VMware
- Product
- VMware Fusion
- Classifications
- CWE-20, T1574
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 3, 2024CVE publishedPublication date reported by the CVE source.
- Sep 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=13.0 <13.6
- Affected versionversion=13.x <13.6
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.
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