Local kernel corruption via arbitrary address write
Published Mar 25, 2023 · Updated Aug 2, 2024
Memory corruption in Jiangmin Antivirus 16.2.2022.418 allows local users to write kernel memory through the kvcore.sys IOCTL handler. The 0x222010 handler accepts a caller-supplied address in its input structure and writes to that address without restricting it to a safe buffer. Local users can open the KvCoreCtrl device and corrupt kernel structures, causing a system crash or enabling broader kernel-memory manipulation.
Summary
What happened
Memory corruption in Jiangmin Antivirus 16.2.2022.418 allows local users to write kernel memory through the kvcore.sys IOCTL handler. The 0x222010 handler accepts a caller-supplied address in its input structure and writes to that address without restricting it to a safe buffer. Local users can open the KvCoreCtrl device and corrupt kernel structures, causing a system crash or enabling broader kernel-memory manipulation.
The record
- CVE
- CVE-2023-1629
- Published
- Mar 25, 2023
- Updated
- Aug 2, 2024
- Vendor
- Jiangmin
- Product
- Jiangmin Antivirus
- Classifications
- CWE-119, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 25, 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=16.2.2022.418
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
- ArbitraryAddressWrite 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