# CVE-2021-28686: Memory corruption in n/a

> Low-privileged users can trigger a stack-based buffer overflow in ASUS GPUTweak II drivers, causing a denial of service.

- **Severity:** Medium 5.5 (`CVSS:3.1/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:** 8 Apr 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-f675-6gv9-54vc

## What is CVE-2021-28686?

CVE-2021-28686 is a medium-severity memory corruption vulnerability in n/a, published on 8 Apr 2021. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

AsIO2_64.sys and AsIO2_32.sys in ASUS GPUTweak II before 2.3.0.3 allow low-privileged users to trigger a stack-based buffer overflow. This could enable low-privileged users to achieve Denial of Service via a DeviceIoControl.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2021-28686?

It affects 1 product.


Products: Asus Gputweak Ii.

## How do I fix CVE-2021-28686?

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

## Is CVE-2021-28686 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-28685](https://insights.sbomify.com/CVE-2021-28685/): Privilege escalation in n/a (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-28686 and fix it if it is affected.

What it is: CVE-2021-28686 is a medium-severity memory corruption vulnerability in n/a, published on 8 Apr 2021. 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-2021-28686 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-2021-28686/ (Markdown: https://insights.sbomify.com/CVE-2021-28686/index.md)
```

## Sources

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

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