Local privilege escalation via unvalidated IOCTL UserBuffer
Published May 24, 2023 · Updated Aug 2, 2024
Memory corruption in Filseclab Corporation Twister Antivirus 8 allows local users to elevate privileges through crafted IOCTL requests. The filppd.sys IOControlCode handler accepts an unvalidated UserBuffer for four affected codes, allowing a normal user to write to an arbitrary kernel address. A standard local account must execute code on the Windows host; the published proof of concept triggers a system crash, while the documented write primitive supports privilege elevation.
Summary
What happened
Memory corruption in Filseclab Corporation Twister Antivirus 8 allows local users to elevate privileges through crafted IOCTL requests. The filppd.sys IOControlCode handler accepts an unvalidated UserBuffer for four affected codes, allowing a normal user to write to an arbitrary kernel address. A standard local account must execute code on the Windows host; the published proof of concept triggers a system crash, while the documented write primitive supports privilege elevation.
The record
- CVE
- CVE-2023-2873
- Published
- May 24, 2023
- Updated
- Aug 2, 2024
- Vendor
- Filseclab Corporation
- Product
- Twister Antivirus
- Classifications
- CWE-787, CWE-119, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 24, 2023CVE publishedPublication date reported by the CVE source.
- Aug 2, 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=8
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
- filppdExploit proof of conceptproof of concept · demonstrated
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