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

> A low-privileged user can exploit insecure permissions to gain SYSTEM level access via the repair function in Crestron AirMedia for Windows.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Sep 2022
- **Updated:** 27 May 2025
- **Also known as:** GHSA-cqmx-6jcw-hqpm

## What is CVE-2022-40298?

CVE-2022-40298 is a high-severity vulnerability in n/a, published on 22 Sep 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Crestron AirMedia for Windows before 5.5.1.84 has insecure inherited permissions, which leads to a privilege escalation vulnerability found in the AirMedia Windows Application, version 4.3.1.39. A low privileged user can initiate a repair of the system and gain a SYSTEM level shell.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

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

It affects 1 product.


Products: Crestron Airmedia.

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

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

## Is CVE-2022-40298 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-34100](https://insights.sbomify.com/CVE-2022-34100/): Privilege escalation in n/a (high 8.8)
- [CVE-2022-34102](https://insights.sbomify.com/CVE-2022-34102/): Privilege escalation in n/a (high 8.8)
- [CVE-2022-34101](https://insights.sbomify.com/CVE-2022-34101/): Privilege escalation in n/a (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-40298 is a high-severity vulnerability in n/a, published on 22 Sep 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-40298 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-40298/ (Markdown: https://insights.sbomify.com/CVE-2022-40298/index.md)
```

## Sources

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

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