# CVE-2022-42455: Privilege escalation in n/a

> Local attackers can exploit unprivileged IOCTL handlers in the ASUS EC Tool driver to gain elevated privileges via raw port and MSR access.

- **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:** 15 Feb 2023
- **Updated:** 19 Mar 2025
- **Also known as:** GHSA-pm9g-2hv5-xfp2

## What is CVE-2022-42455?

CVE-2022-42455 is a high-severity vulnerability in n/a, published on 15 Feb 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

ASUS EC Tool driver (aka d.sys) 1beb15c90dcf7a5234ed077833a0a3e900969b60be1d04fcebce0a9f8994bdbb, as signed by ASUS and shipped with multiple ASUS software products, contains multiple IOCTL handlers that provide raw read and write access to port I/O and MSRs via unprivileged IOCTL calls. Local users can gain privileges.

Weakness: CWE-269 (Improper Privilege Management)

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

It affects 1 product.


Products: Asus Armoury Crate.

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

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

## Is CVE-2022-42455 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-5716](https://insights.sbomify.com/CVE-2023-5716/): ASUS Armoury Crate - Arbitrary File Write (critical 9.8)
- [CVE-2023-26911](https://insights.sbomify.com/CVE-2023-26911/): Privilege escalation in n/a (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-42455 is a high-severity vulnerability in n/a, published on 15 Feb 2023. 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-2022-42455 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-2022-42455/ (Markdown: https://insights.sbomify.com/CVE-2022-42455/index.md)
```

## Sources

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

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