PT-2020-6777 · Xen+1 · Xen+1

Pawel Wieczorkiewicz

·

Published

2020-12-15

·

Updated

2024-06-15

·

CVE-2020-29483

CVSS v3.1

6.5

Medium

VectorAV:L/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H
Name of the Vulnerable Software and Affected Versions Xen versions through 4.14.x
Description An issue was discovered in Xen where xenstored and guests communicate via a shared memory page using a specific protocol. When a guest violates this protocol, xenstored will drop the connection to that guest, resulting in the same actions as if the guest had been destroyed, including sending an @releaseDomain event. This can lead to a zombie domain, where memory mappings of that guest's memory will not be removed due to the missing event. A malicious guest can block resources of the host for a period after its own death. Guests with a stub domain device model can eventually crash xenstored, resulting in a more serious denial of service. Only the C variant of Xenstore is affected, and only HVM guests with a stubdom device model can cause a serious DoS.
Recommendations To resolve the issue, update to a version of Xen that is not affected by this issue. As a temporary workaround, consider restricting the use of the @releaseDomain event to minimize the risk of exploitation. Restrict access to the xenstored internal management to prevent a malicious guest from blocking resources of the host. Avoid using the stub domain device model for HVM guests until the issue is resolved. At the moment, there is no information about a newer version that contains a fix for this vulnerability.

DoS

Improper Resource Release

Use After Free

Found an issue in the description? Have something to add? Feel free to write us 👾

Weakness Enumeration

Related Identifiers

BDU:2022-06301
CVE-2020-29483
DSA-4812-1
OPENSUSE-SU-2020:2313-1
OPENSUSE-SU-2020:2331-1
OPENSUSE-SU-2020_2313-1
OPENSUSE-SU-2020_2331-1
OPENSUSE-SU-2024:11520-1
SUSE-SU-2020:14578-1
SUSE-SU-2020:3880-1
SUSE-SU-2020:3881-1
SUSE-SU-2020:3913-1
SUSE-SU-2020:3914-1
SUSE-SU-2020:3915-1
SUSE-SU-2020:3916-1
SUSE-SU-2020:3945-1
SUSE-SU-2020_14578-1

Affected Products

Suse
Xen