Sandbox escape via VMX out-of-bounds write
Published Mar 5, 2024 · Updated Aug 14, 2024
Out-of-bounds write in VMware ESXi 7.0 and 8.0 allows local users with VMX-process privileges to escape the VMX sandbox. VMware identifies the faulty locus only as the VMX process and has not disclosed the affected buffer, input, or operation that writes past its boundary. Successful exploitation enables access to and modification of host-context data; Cloud Foundation is affected through its ESXi component.
Summary
What happened
Out-of-bounds write in VMware ESXi 7.0 and 8.0 allows local users with VMX-process privileges to escape the VMX sandbox. VMware identifies the faulty locus only as the VMX process and has not disclosed the affected buffer, input, or operation that writes past its boundary. Successful exploitation enables access to and modification of host-context data; Cloud Foundation is affected through its ESXi component.
The record
- CVE
- CVE-2024-22254
- Published
- Mar 5, 2024
- Updated
- Aug 14, 2024
- Vendor
- VMware
- Product
- VMware Cloud Foundation
- Classifications
- CWE-787, T1611
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Mar 5, 2024CVE publishedPublication date reported by the CVE source.
- Aug 14, 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=4.0
- Affected versionversion=4.x
- Affected versionversion=5.0
- Affected versionversion=5.x
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