Skip to content

GHSA-c7w7-9c85-4qxv CVE-2020-17376 PYSEC-2020-243

OpenStack Nova Live migration fails to update persistent domain XML

High PyPI
Severity
0.0 / 10
High · CVSS 4.0
Exploit chance (EPSS)
1.73%
Chance of exploitation in the next 30 days. Higher than 77.59% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-611 Improper Restriction of XML External Entity Reference
Fix
19.3.1
Upgrade nova to this version or later

Description

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.

Affected versions

PyPI

PackageVulnerableFixed in
nova
< 19.3.1
19.3.1
nova
>= 20.0.0, < 20.3.1
20.3.1
nova 1 listed versions No fix yet
nova
< 19.3.1
>= 20.0.0, < 20.3.1
>= 21.0.0, < 21.1.0
19.3.1
20.3.1
21.1.0

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

nova PyPI → 19.3.1

pip
pip install --upgrade "nova>=19.3.1"
poetry
poetry add "nova>=19.3.1"
uv
uv add "nova>=19.3.1"

Severity breakdown

CVSS 4.0 0.0

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N

Attack vector
Network
Attack complexity
Low
Attack requirements
None
Privileges required
Low
User interaction
None
Confidentiality (vulnerable system)
High
Integrity (vulnerable system)
High
Availability (vulnerable system)
Low
Confidentiality (subsequent systems)
None
Integrity (subsequent systems)
None
Availability (subsequent systems)
None

CVSS 3.1 8.3

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
Low

Weakness

CWE-611: Improper Restriction of XML External Entity Reference

The product processes an XML document that can contain XML entities with URIs that resolve to documents outside of the intended sphere of control, causing the product to embed incorrect documents into its output.

How to prevent it
  • Implementation, System Configuration: Many XML parsers and validators can be configured to disable external entity expansion.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-mfg3-p6m3-gjgr
OpenStack Nova: Nova scheduler hint injection bypasses Placement resource claims and scheduling constraints
High Also affects nova
GHSA-m4f3-qp2w-gwh6
OpenStack Nova calls qemu-img without format restrictions for resize
High Also affects nova
GHSA-rm86-h44c-2r2m
OpenStack Nova vulnerable to unauthorized access to potentially sensitive data
Medium Also affects nova
GHSA-r4v4-w9pv-6fph
OpenStack Cinder, Glance, and Nova vulnerable to arbitrary file access
Medium Also affects nova
GHSA-7h75-hwxx-qpgc
OpenStack Cinder, glance, and Nova vulnerable to Path Traversal
Medium Also affects nova
GHSA-v725-c588-h936
OpenStack Nova Changing vnic_type breaks compute service restart
Low Also affects nova
GHSA-22jm-4hxw-35jf
OpenStack Nova can leak consoleauth token into log files
Low Also affects nova
GHSA-43cm-73px-5v4m
OpenStack Compute (Nova) Resource limit circumvention in Nova private flavors
Low Also affects nova
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor