# CVE-2022-21933: ASUS VivoMini/Mini PC - improper input validation

> A local attacker with system privileges can exploit improper input validation in ASUS Mini PC firmware to achieve arbitrary code execution and control the system.

- **Severity:** Medium 6.7 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Jan 2022
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-qjg9-wm29-5rcr

## What is CVE-2022-21933?

CVE-2022-21933 is a medium-severity memory corruption vulnerability in ASUS PA90, published on 21 Jan 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

ASUS VivoMini/Mini PC device has an improper input validation vulnerability. A local attacker with system privilege can use system management interrupt (SMI) to modify memory, resulting in arbitrary code execution for controlling the system or disrupting service.

Weakness: CWE-787 (Out-of-bounds Write), CWE-20 (Improper Input Validation)

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

It affects 13 products.


Products: Asus Pa90 Firmware, Asus Pb50 Firmware, Asus Pb60 Firmware, Asus Pb60g Firmware, Asus Pb60s Firmware, Asus Pb60v Firmware, Asus Pb61v Firmware, Asus Pn30 Firmware, Asus Pn40 Firmware, Asus Pn60 Firmware, Asus Ts10 Firmware, Asus Un65u Firmware, Asus Vc65-C1 Firmware.

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

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

## Is CVE-2022-21933 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-21933 is a medium-severity memory corruption vulnerability in ASUS PA90, published on 21 Jan 2022. 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-21933 in the wild and no public exploit code.

Affected product: ASUS PA90. 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-21933/ (Markdown: https://insights.sbomify.com/CVE-2022-21933/index.md)
```

## Sources

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

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