Kernel memory disclosure via unchecked IOCTL offset
Published Mar 20, 2020 · Updated Aug 5, 2024
Out-of-bounds read in Rivet Killer Control Center before 2.1.1352 allows local users with admin rights to read kernel memory via a driver request. The KfeCo10X64.sys handler for IOCTL 0x120404 uses an attacker-supplied offset for a memory operation without validation, allowing the read to cross the intended buffer boundary. Administrator access is required, and the disclosed primitive supports privilege escalation only when chained with other flaws.
Summary
What happened
Out-of-bounds read in Rivet Killer Control Center before 2.1.1352 allows local users with admin rights to read kernel memory via a driver request. The KfeCo10X64.sys handler for IOCTL 0x120404 uses an attacker-supplied offset for a memory operation without validation, allowing the read to cross the intended buffer boundary. Administrator access is required, and the disclosed primitive supports privilege escalation only when chained with other flaws.
The record
- CVE
- CVE-2019-15663
- Published
- Mar 20, 2020
- Updated
- Aug 5, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-125, T1068
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Mar 20, 2020CVE publishedPublication date reported by the CVE source.
- Aug 5, 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.
Public exploit references
- FEYE-2019-0007 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