Privilege escalation via incorrect wide-character writes
Published Nov 17, 2021 · Updated Aug 3, 2024
Integer overflow in Intel SafeString Library before commit efbd4066 allows local users to escalate privileges. The wmemset_s function always calls mem_prim_set32 even when wchar_t is 16 bits, writing four-byte values into two-byte elements. Exploitation requires low-privileged local access, high complexity, and user interaction; the crossed privilege boundary is undisclosed.
Summary
What happened
Integer overflow in Intel SafeString Library before commit efbd4066 allows local users to escalate privileges. The wmemset_s function always calls mem_prim_set32 even when wchar_t is 16 bits, writing four-byte values into two-byte elements. Exploitation requires low-privileged local access, high complexity, and user interaction; the crossed privilege boundary is undisclosed.
The record
- CVE
- CVE-2021-33106
- Published
- Nov 17, 2021
- Updated
- Aug 3, 2024
- Vendor
- Intel
- Product
- SafeString Library
- Classifications
- CWE-190, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 17, 2021CVE 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=See references
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.
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