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

> A low-privileged user can gain SYSTEM level command prompt access by manipulating file structures during a repair operation in the Crestron AirMedia Windows Application.

- **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:** 13 Sep 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-9hpv-x27v-56h8

## What is CVE-2022-34100?

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

### Official description

A vulnerability was discovered in the Crestron AirMedia Windows Application, version 4.3.1.39, in which a low-privileged user can gain a SYSTEM level command prompt by pre-staging a file structure prior to the installation of a trusted service executable and change permissions on that file structure during a repair operation.

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

It affects 1 product.


Products: Crestron Airmedia.

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

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

## Is CVE-2022-34100 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-40298](https://insights.sbomify.com/CVE-2022-40298/): 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-34100 and fix it if it is affected.

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

## Sources

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

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