Host privilege escalation via exposed settingsd tickets
Published Feb 16, 2022 · Updated Aug 3, 2024
Incorrect authorization in VMware ESXi 7.0 Update 1 through Update 3 allows local users to access settingsd with elevated privileges. The VMX process can obtain settingsd authorization tickets that cross the intended privilege boundary and submit them to the high-privilege service. Exploitation requires existing control of the VMX process; the resulting access permits settingsd operations with host-level authority.
Summary
What happened
Incorrect authorization in VMware ESXi 7.0 Update 1 through Update 3 allows local users to access settingsd with elevated privileges. The VMX process can obtain settingsd authorization tickets that cross the intended privilege boundary and submit them to the high-privilege service. Exploitation requires existing control of the VMX process; the resulting access permits settingsd operations with host-level authority.
The record
- CVE
- CVE-2021-22042
- Published
- Feb 16, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-863, T1068
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Feb 16, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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
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