System crash via kvcore.sys null pointer dereference
Published Mar 25, 2023 · Updated Feb 19, 2025
Null pointer dereference in the kvcore.sys IOCTL handler in Jianming Antivirus 16.2.2022.418 allows local users to crash the system. The public record does not identify the handler function, IOCTL code, or input that reaches the null dereference in the Windows kernel driver. Low-privilege local access is required, and successful triggering interrupts system availability without reported data disclosure or modification.
Summary
What happened
Null pointer dereference in the kvcore.sys IOCTL handler in Jianming Antivirus 16.2.2022.418 allows local users to crash the system. The public record does not identify the handler function, IOCTL code, or input that reaches the null dereference in the Windows kernel driver. Low-privilege local access is required, and successful triggering interrupts system availability without reported data disclosure or modification.
The record
- CVE
- CVE-2023-1628
- Published
- Mar 25, 2023
- Updated
- Feb 19, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-476, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 25, 2023CVE publishedPublication date reported by the CVE source.
- Feb 19, 2025Record 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
- Jianming Antivirus kvcore.sys proof of conceptproof of concept · unverified
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