CVE-2020-17376: n/a vulnerability

CVE-2020-17376: An issue was discovered in Guest.migrate in virt/libvirt/guest.py in OpenStack Nova before 19.3.1, 20.x bef...

An issue was discovered in Guest.migrate in virt/libvirt/guest.py in OpenStack Nova before 19.3.1, 20.x before 20.3.1, and 21.0.0. By performing a soft reboot of an instance that has previously undergone live migration, a user may gain access to destination host devices that share the same paths as host devices previously referenced by the virtual machine on the source host. This can include block devices that map to different Cinder volumes at the destination than at the source. Only deployments allowing host-based connections (for instance, root and ephemeral devices) are affected.

UnknownCVSS not scoredNot KEV-listedUpdatedAug 4, 2024, 13:53 UTC (UTC+00:00)

Security readout for executives and security teams

This Nova flaw can let a cloud tenant access storage devices on a destination compute host after a live-migrated instance later reboots. In affected OpenStack deployments, that could expose another Cinder volume or host-backed device. The issue is narrow but serious for multi-tenant clouds because it crosses expected tenant storage boundaries. Exposure is limited to OpenStack Nova deployments using libvirt and allowing host-based connections, such as root and ephemeral devices. Systems are most relevant if they run the listed affected Nova versions and perform live migration of tenant instances. Treat this as high priority for OpenStack clouds with multi-tenant workloads and live migration. The impact is potential cross-tenant storage exposure, but applicability is narrower than an internet-facing remote code execution issue. Confirm exposure first, then patch affected Nova releases quickly. Mitigation focus: Upgrade Nova away from the listed affected versions using vendor-supported fixed packages.; Apply fixes referenced by OpenStack OSSA-2020-006 or distribution backports.; Review whether host-based connections are enabled and restrict them where operationally possible..

Prepared: Jun 3, 2026, 10:39 UTC (UTC+00:00)

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2020-17376 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup

Vulnerability profileCVE Program record

Severity: Unknown
CVSS: Not scored
Known Exploited: No
Published: Aug 26, 2020, 18:45 UTC (UTC+00:00)

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors

0Timeline events

0ADP providers

3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

CVE List V5 sourceCVE List V5
https://launchpad.net/bugs/1890501CVE reference · x_refsource_MISC
https://security.openstack.org/ossa/OSSA-2020-006.htmlCVE reference · x_refsource_CONFIRM

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus

n/an/an/aListed

Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.