# CVE-2022-24543: Windows Upgrade Assistant Remote Code Execution Vulnerability

> An attacker can execute arbitrary code via the Windows Upgrade Assistant, requiring immediate patching by system administrators.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 15 Apr 2022
- **Updated:** 2 Jan 2025
- **Also known as:** GHSA-jm4q-r2cm-cjq2

## What is CVE-2022-24543?

CVE-2022-24543 is a high-severity code injection vulnerability in Microsoft Windows Upgrade Assistant, published on 15 Apr 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Windows Upgrade Assistant Remote Code Execution Vulnerability

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

It affects 1 product.


Products: Microsoft Windows Upgrade Assistant.

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

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

## Is CVE-2022-24543 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-24543 is a high-severity code injection vulnerability in Microsoft Windows Upgrade Assistant, published on 15 Apr 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-24543 in the wild and no public exploit code.

Affected product: Microsoft Windows Upgrade Assistant. 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-24543/ (Markdown: https://insights.sbomify.com/CVE-2022-24543/index.md)
```

## Sources

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

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