# CVE-2018-10828: Denial of service in n/a

> A local attacker can cause a denial of service by writing invalid pointers to a shared memory section in the Alps Pointing-device Driver.

- **Severity:** Medium 5.5 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 May 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-vm26-wqqf-xxff

## What is CVE-2018-10828?

CVE-2018-10828 is a medium-severity denial of service vulnerability in n/a, published on 9 May 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue was discovered in Alps Pointing-device Driver 10.1.101.207. ApMsgFwd.exe allows the current user to map and write to the "ApMsgFwd File Mapping Object" section. ApMsgFwd.exe uses the data written to this section as arguments to functions. This causes a denial of service condition when invalid pointers are written to the mapped section. This driver has been used with Dell, ThinkPad, and VAIO devices.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2018-10828?

It affects 1 product.


Products: Alps Pointing-Device Driver.

## How do I fix CVE-2018-10828?

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

## Is CVE-2018-10828 being exploited?

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

Public exploit code:

- Dell Touchpad - 'ApMsgFwd.exe' Denial of Service (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-10828 and fix it if it is affected.

What it is: CVE-2018-10828 is a medium-severity denial of service vulnerability in n/a, published on 9 May 2018. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-10828 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-2018-10828/ (Markdown: https://insights.sbomify.com/CVE-2018-10828/index.md)
```

## Sources

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

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