# CVE-2023-45883: Privilege escalation in n/a

> Standard users can gain SYSTEM privileges and execute arbitrary code by triggering a software repair in Qumu Multicast Extension.

- **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:** 19 Oct 2023
- **Updated:** 12 Sep 2024
- **Also known as:** GHSA-2fcg-hwv9-g767

## What is CVE-2023-45883?

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

### Official description

A privilege escalation vulnerability exists within the Qumu Multicast Extension v2 before 2.0.63 for Windows. When a standard user triggers a repair of the software, a pop-up window opens with SYSTEM privileges. Standard users may use this to gain arbitrary code execution as SYSTEM.

Weakness: CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2023-45883?

It affects 1 product.


Products: Enghouse Qumu.

## How do I fix CVE-2023-45883?

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

## Is CVE-2023-45883 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-45883 and fix it if it is affected.

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

## Sources

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

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