# CVE-2020-10731: Misconfiguration in nova libvirt container provided by the Red Hat OpenStack Platform

> The nova_libvirt container lacks SELinux, disabling sVirt isolation for virtual machines and allowing potential security bypasses.

- **Severity:** Critical 9.9 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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:** Yes
- **Published:** 31 Jul 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-9m56-29jp-mr7j, RHSA-2020:3199, RHSA-2020:3406, RHSA-2020:3410

## What is CVE-2020-10731?

CVE-2020-10731 is a critical vulnerability in nova_libvirt container provided by the Red Hat OpenStack Platform, published on 31 Jul 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A flaw was found in the nova_libvirt container provided by the Red Hat OpenStack Platform 16, where it does not have SELinux enabled. This flaw causes sVirt, an important isolation mechanism, to be disabled for all running virtual machines.

Weakness: CWE-284 (Improper Access Control)

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `openstack-tripleo-heat-templates` | Red Hat:openstack:15::el8 | All versions | 0:10.6.3-0.20200113185561.cf467ea.el8ost |
| `paunch-services` | Red Hat:openstack:15::el8 | All versions | 0:4.5.3-0.20200108190460.3c38fe6.el8ost |
| `python-paunch` | Red Hat:openstack:15::el8 | All versions | 0:4.5.3-0.20200108190460.3c38fe6.el8ost |
| `python3-paunch` | Red Hat:openstack:15::el8 | All versions | 0:4.5.3-0.20200108190460.3c38fe6.el8ost |
| `openstack-tripleo-heat-templates` | Red Hat:openstack:16.1::el8 | All versions | 0:11.3.2-0.20200616081532.396affd.el8ost |
| `openstack-tripleo-heat-templates` | Red Hat:openstack:16::el8 | All versions | 0:11.3.2-0.20200405044628.ec9970c.el8ost |
| `paunch-services` | Red Hat:openstack:16::el8 | All versions | 0:5.3.2-0.20200320172310.ebc49c4.el8ost |
| `python-paunch` | Red Hat:openstack:16::el8 | All versions | 0:5.3.2-0.20200320172310.ebc49c4.el8ost |
| `python3-paunch` | Red Hat:openstack:16::el8 | All versions | 0:5.3.2-0.20200320172310.ebc49c4.el8ost |

Products: Redhat Openstack Platform.

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

Apply the vendor's patch.

## Is CVE-2020-10731 being exploited?

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

## Other vulnerabilities in nova_libvirt container provided by the Red Hat OpenStack Platform

- [CVE-2024-8007](https://insights.sbomify.com/CVE-2024-8007/): Openstack-tripleo-common: rhosp director disables tls verification for registry mirrors (high 8.1)
- [CVE-2017-15114](https://insights.sbomify.com/CVE-2017-15114/): Missing authorization in n/a (high 8.1)
- [CVE-2022-3596](https://insights.sbomify.com/CVE-2022-3596/): Instack-undercloud: rsync leaks information to undercloud (high 7.5)
- [CVE-2023-6725](https://insights.sbomify.com/CVE-2023-6725/): Tripleo-ansible: bind keys are world readable (medium 5.5)
- [CVE-2022-3261](https://insights.sbomify.com/CVE-2022-3261/): Plain-text passwords saved in /var/log/messages (medium 4.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-10731 is a critical vulnerability in nova_libvirt container provided by the Red Hat OpenStack Platform, published on 31 Jul 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-10731 in the wild and no public exploit code.

Affected product: nova_libvirt container provided by the Red Hat OpenStack Platform. 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-10731/ (Markdown: https://insights.sbomify.com/CVE-2020-10731/index.md)
```

## Sources

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

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