# CVE-2019-15664: Memory corruption in n/a

> An out-of-bounds read in the Killer Control Center driver allows attackers to escalate privileges via a specific IOCTL call.

- **Severity:** Low 2.7 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Mar 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-6jq9-5c82-pc83

## What is CVE-2019-15664?

CVE-2019-15664 is a low-severity memory corruption vulnerability in n/a, published on 20 Mar 2020. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

An issue was discovered in Rivet Killer Control Center before 2.1.1352. IOCTL 0x120404 in KfeCo10X64.sys fails to validate an offset passed as a parameter during a memory operation, leading to an out-of-bounds read that can be used as part of a chain to escalate privileges (issue 2 of 2).

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2019-15664?

It affects 1 product.


Products: Killernetworking Killer Control Center.

## How do I fix CVE-2019-15664?

No fix has been published for CVE-2019-15664 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-15664 being exploited?

There is no known exploitation of CVE-2019-15664 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2019-15661](https://insights.sbomify.com/CVE-2019-15661/): Memory corruption in n/a (high 7.2)
- [CVE-2019-15665](https://insights.sbomify.com/CVE-2019-15665/): Memory corruption in n/a (high 7.2)
- [CVE-2019-15662](https://insights.sbomify.com/CVE-2019-15662/): Memory corruption in n/a (low 2.7)
- [CVE-2019-15663](https://insights.sbomify.com/CVE-2019-15663/): Memory corruption in n/a (low 2.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-15664 and fix it if it is affected.

What it is: CVE-2019-15664 is a low-severity memory corruption vulnerability in n/a, published on 20 Mar 2020. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-15664 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-15664/ (Markdown: https://insights.sbomify.com/CVE-2019-15664/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-15664
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-15664
- OSV: https://osv.dev/vulnerability/CVE-2019-15664

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-15664/
Summaries are generated and may contain mistakes; the official description above is the record.