CVE-2019-15665
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn issue was discovered in Rivet Killer Control Center before 2.1.1352. IOCTL 0x120004 in KfeCo10X64.sys fails to validate an offset passed as a parameter during a memory operation, leading to an arbitrary write primitive that can lead to code execution or escalation of privileges.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe KfeCo10X64.sys kernel driver in Rivet Killer Control Center contains an arbitrary memory write vulnerability in IOCTL handler 0x120004. The handler fails to validate an offset parameter before using it in a memory operation, allowing an unprivileged local attacker to write arbitrary data to arbitrary memory locations and achieve code execution or local privilege escalation.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 2.1.1352CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check if KfeCo10X64.sys driver is present on the systemOpen File Explorer and navigate to C:\Windows\System32\drivers\, or search for KfeCo10X64.sys. Alternatively, open an elevated command prompt and run: dir C:\Windows\System32\drivers\KfeCo10X64.sysAffected if The file KfeCo10X64.sys exists in the drivers directory, indicating the vulnerable driver is installed
-
Obtain the file version of the kernel driverRight-click on KfeCo10X64.sys, select Properties, then go to the Details tab and note the File version. Alternatively, run this PowerShell command: (Get-Item 'C:\Windows\System32\drivers\KfeCo10X64.sys').VersionInfo | Select-Object FileVersionAffected if The driver file exists and its version is lower than 2.1.1352 (or the version field cannot be determined, suggesting an unpatched build)
-
Check if the Killer Control Center application is installed and its versionOpen Programs and Features (appwiz.cpl) and look for 'Killer Control Center' or 'Rivet Killer Control Center', or run: Get-WmiObject -Class Win32_Product | Where-Object {$_.Name -like '*Killer*'} | Select-Object Name, VersionAffected if The application is installed with a version listed as less than 2.1.1352
-
Verify the driver is currently loaded in memoryOpen an elevated command prompt and run: sc query KfeCo10X64 or check Device Manager under 'System devices' for 'Killer Wireless Channel Switch' or similar Rivet/Killer network devicesAffected if The driver service exists and shows a state other than 'STOPPED', meaning the vulnerable code path could potentially be reached
If the KfeCo10X64.sys driver is present and either the driver file version or the Killer Control Center application version is below 2.1.1352, the system is vulnerable to local privilege escalation via the unchecked IOCTL 0x120004 handler.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data2.1.1352
Update Rivet Killer Control Center to version 2.1.1352 or later to obtain the patched kernel driver that properly validates offset parameters in IOCTL handlers.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-15665 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-15665 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data