# CVE-2020-23793: Missing authorization in n/a

> An attacker can restart KVM virtual machines without authorization in Red Hat's VDI product, causing service disruption.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Aug 2023
- **Updated:** 3 Oct 2024
- **Also known as:** DEBIAN-CVE-2020-23793, GHSA-76gg-j5fc-hc83, UBUNTU-CVE-2020-23793

## What is CVE-2020-23793?

CVE-2020-23793 is a high-severity missing authorization vulnerability in n/a, published on 22 Aug 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in spice-server spice-server-0.14.0-6.el7_6.1.x86_64 of Redhat's VDI product. There is a security vulnerablility that can restart KVMvirtual machine without any authorization. It is not yet known if there will be other other effects.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2020-23793?

It affects 1 product.


Products: Spice-Space Spice-Server.

## How do I fix CVE-2020-23793?

Apply the vendor's patch.

## Is CVE-2020-23793 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-23793 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-23793 and fix it if it is affected.

What it is: CVE-2020-23793 is a high-severity missing authorization vulnerability in n/a, published on 22 Aug 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-23793 exists.

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-2020-23793/ (Markdown: https://insights.sbomify.com/CVE-2020-23793/index.md)
```

## Sources

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

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