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

> A pool overflow in Asus Precision TouchPad drivers allows local attackers to cause denial of service or escalate privileges via crafted device control calls.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Sep 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-9g89-gm6j-67rj

## What is CVE-2019-10709?

CVE-2019-10709 is a critical memory corruption vulnerability in n/a, published on 4 Sep 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

AsusPTPFilter.sys on Asus Precision TouchPad 11.0.0.25 hardware has a Pool Overflow associated with the \\.\AsusTP device, leading to a DoS or potentially privilege escalation via a crafted DeviceIoControl call.

Weakness: CWE-264

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

It affects 1 product.


Products: Asus Precision Touchpad.

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

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

## Is CVE-2019-10709 being exploited?

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

Public exploit code:

- Asus Precision TouchPad 11.0.0.25 - Denial of Service (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-10709 is a critical memory corruption vulnerability in n/a, published on 4 Sep 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-10709 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-10709/ (Markdown: https://insights.sbomify.com/CVE-2019-10709/index.md)
```

## Sources

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

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