Privilege escalation via unchecked driver IOCTL offset
Published Mar 20, 2020 · Updated Aug 5, 2024
Out-of-bounds write in KfeCo10X64.sys in Rivet Killer Control Center before 2.1.1352 allows attackers to escalate privileges via IOCTL input. The driver handles IOCTL 0x120004 without validating a caller-supplied offset before a memory operation, creating an arbitrary write primitive. Exploitation requires high privileges and access to the driver interface; the write can corrupt kernel memory and execute code with greater privileges.
Summary
What happened
Out-of-bounds write in KfeCo10X64.sys in Rivet Killer Control Center before 2.1.1352 allows attackers to escalate privileges via IOCTL input. The driver handles IOCTL 0x120004 without validating a caller-supplied offset before a memory operation, creating an arbitrary write primitive. Exploitation requires high privileges and access to the driver interface; the write can corrupt kernel memory and execute code with greater privileges.
The record
- CVE
- CVE-2019-15665
- Published
- Mar 20, 2020
- Updated
- Aug 5, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1068
- Attack vector
- network
- 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
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