Local memory corruption via driver control handling
Published Mar 25, 2023 · Updated Aug 2, 2024
Memory corruption in the kvcore.sys driver in Jianming Antivirus 16.2.2022.418 allows local users to corrupt kernel memory. The published record identifies the IoControlCode handler but does not disclose the specific control code, memory operation, or corrupted object. Low-privileged local access is required, and the disclosed evidence establishes no consequence more specific than limited confidentiality, integrity, and availability impact.
Summary
What happened
Memory corruption in the kvcore.sys driver in Jianming Antivirus 16.2.2022.418 allows local users to corrupt kernel memory. The published record identifies the IoControlCode handler but does not disclose the specific control code, memory operation, or corrupted object. Low-privileged local access is required, and the disclosed evidence establishes no consequence more specific than limited confidentiality, integrity, and availability impact.
The record
- CVE
- CVE-2023-1626
- Published
- Mar 25, 2023
- Updated
- Aug 2, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-119
- 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?
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