# CVE-2022-44898: Memory corruption in n/a

> Attackers can trigger memory corruption in the Asus Aura Sync driver via crafted IOCTL requests, leading to privilege escalation or denial of service.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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:** 14 Dec 2022
- **Updated:** 22 Apr 2025
- **Also known as:** GHSA-873m-q6f6-cfqx

## What is CVE-2022-44898?

CVE-2022-44898 is a high-severity memory corruption vulnerability in n/a, published on 14 Dec 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The MsIo64.sys component in Asus Aura Sync through v1.07.79 does not properly validate input to IOCTL 0x80102040, 0x80102044, 0x80102050, and 0x80102054, allowing attackers to trigger a memory corruption and cause a Denial of Service (DoS) or escalate privileges via crafted IOCTL requests.

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

## Which versions are affected by CVE-2022-44898?

It affects 1 product.


Products: Asus Aura Sync.

## How do I fix CVE-2022-44898?

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

## Is CVE-2022-44898 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-44898 exists.

## Other vulnerabilities in n/a

- [CVE-2019-17603](https://insights.sbomify.com/CVE-2019-17603/): Memory corruption in n/a (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-44898 and fix it if it is affected.

What it is: CVE-2022-44898 is a high-severity memory corruption vulnerability in n/a, published on 14 Dec 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-44898 exists.

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-2022-44898/ (Markdown: https://insights.sbomify.com/CVE-2022-44898/index.md)
```

## Sources

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

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