CVE-2020-15566
published 2020-07-07CVE-2020-15566: An issue was discovered in Xen through 4.13.x, allowing guest OS users to cause a host OS crash because of incorrect error handling in event-channel port…
PriorityP426medium6.5CVSS 3.1
AVLACLPRLUINSCCNINAH
EPSS
0.41%
33.5th percentile
An issue was discovered in Xen through 4.13.x, allowing guest OS users to cause a host OS crash because of incorrect error handling in event-channel port allocation. The allocation of an event-channel port may fail for multiple reasons: (1) port is already in use, (2) the memory allocation failed, or (3) the port we try to allocate is higher than what is supported by the ABI (e.g., 2L or FIFO) used by the guest or the limit set by an administrator (max_event_channels in xl cfg). Due to the missing error checks, only (1) will be considered an error. All the other cases will provide a valid port and will result in a crash when trying to access the event channel. When the administrator configured a guest to allow more than 1023 event channels, that guest may be able to crash the host. When Xen is out-of-memory, allocation of new event channels will result in crashing the host rather than reporting an error. Xen versions 4.10 and later are affected. All architectures are affected. The default configuration, when guests are created with xl/libxl, is not vulnerable, because of the default event-channel limit.
Affected
8 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | debian_linux | — | — |
| debian | xen | < xen 4.11.4+24-gddaaccbbab-1 (bookworm) | xen 4.11.4+24-gddaaccbbab-1 (bookworm) |
| xen | xen | >= 0 < 4.11.4+24-gddaaccbbab-1 | 4.11.4+24-gddaaccbbab-1 |
| xen | xen | >= 0 < 4.11.4+24-gddaaccbbab-1 | 4.11.4+24-gddaaccbbab-1 |
| xen | xen | >= 0 < 4.11.4+24-gddaaccbbab-1 | 4.11.4+24-gddaaccbbab-1 |
| xen | xen | >= 0 < 4.11.4+24-gddaaccbbab-1 | 4.11.4+24-gddaaccbbab-1 |
| xen | xen | >= 0 < 4.11.3+24-g14b62ab3e5-1ubuntu2.3 | 4.11.3+24-g14b62ab3e5-1ubuntu2.3 |
| xen | xen | 4.10.0 – 4.13.1 | — |
CVSS provenance
nvdv3.16.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H
nvdv2.04.7MEDIUMAV:L/AC:M/Au:N/C:N/I:N/A:C
osv6.5MEDIUM
vendor_debian6.5MEDIUM
vendor_redhat6.5MEDIUM
vendor_ubuntu5.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Ubuntu
Xen vulnerabilities
vendor_ubuntu·2022-09-19·CVSS 5.5
CVE-2020-25599 [MEDIUM] Xen vulnerabilities
Title: Xen vulnerabilities
Summary: Several security issues were fixed in Xen.
It was discovered that memory contents previously stored in
microarchitectural special registers after RDRAND, RDSEED, and SGX EGETKEY
read operations on Intel client and Xeon E3 processors may be briefly
exposed to processes on the same or different processor cores. A local
attacker could use this to expose sensitive information. (CVE-2020-0543)
Julien Grall discovered that Xen incorrectly handled memory barriers on
ARM-based systems. An attacker could possibly use this issue to cause a
denial of service, obtain sensitive information or escalate privileges.
(CVE-2020-11739)
Ilja Van Sprundel discovered that Xen incorrectly handled profiling of
guests. An unprivileged attacker could use this issue to obtain
Red Hat
xen: incorrect error handling in event channel port allocation leads to DoS (XSA-317)
vendor_redhat·2020-07-07·CVSS 6.5
CVE-2020-15566 [MEDIUM] CWE-392 xen: incorrect error handling in event channel port allocation leads to DoS (XSA-317)
xen: incorrect error handling in event channel port allocation leads to DoS (XSA-317)
An issue was discovered in Xen through 4.13.x, allowing guest OS users to cause a host OS crash because of incorrect error handling in event-channel port allocation. The allocation of an event-channel port may fail for multiple reasons: (1) port is already in use, (2) the memory allocation failed, or (3) the port we try to allocate is higher than what is supported by the ABI (e.g., 2L or FIFO) used by the guest or the limit set by an administrator (max_event_channels in xl cfg). Due to the missing error checks, only (1) will be considered an error. All the other cases will provide a valid port and will result in a crash when trying to access the event channel. When the administrator configured a guest to
Debian
CVE-2020-15566: xen - An issue was discovered in Xen through 4.13.x, allowing guest OS users to cause ...
vendor_debian·2020·CVSS 6.5
CVE-2020-15566 [MEDIUM] CVE-2020-15566: xen - An issue was discovered in Xen through 4.13.x, allowing guest OS users to cause ...
An issue was discovered in Xen through 4.13.x, allowing guest OS users to cause a host OS crash because of incorrect error handling in event-channel port allocation. The allocation of an event-channel port may fail for multiple reasons: (1) port is already in use, (2) the memory allocation failed, or (3) the port we try to allocate is higher than what is supported by the ABI (e.g., 2L or FIFO) used by the guest or the limit set by an administrator (max_event_channels in xl cfg). Due to the missing error checks, only (1) will be considered an error. All the other cases will provide a valid port and will result in a crash when trying to access the event channel. When the administrator configured a guest to allow more than 1023 event channels, that guest may be able to crash the host. When Xe
OSV
xen vulnerabilities
osv·2022-09-19·CVSS 5.5
CVE-2020-0543 [MEDIUM] xen vulnerabilities
xen vulnerabilities
It was discovered that memory contents previously stored in
microarchitectural special registers after RDRAND, RDSEED, and SGX EGETKEY
read operations on Intel client and Xeon E3 processors may be briefly
exposed to processes on the same or different processor cores. A local
attacker could use this to expose sensitive information. (CVE-2020-0543)
Julien Grall discovered that Xen incorrectly handled memory barriers on
ARM-based systems. An attacker could possibly use this issue to cause a
denial of service, obtain sensitive information or escalate privileges.
(CVE-2020-11739)
Ilja Van Sprundel discovered that Xen incorrectly handled profiling of
guests. An unprivileged attacker could use this issue to obtain sensitive
information from other guests, cause a denial of s
GHSA
GHSA-2v7g-8jvx-2wfc: An issue was discovered in Xen through 4
ghsa_unreviewed·2022-05-24
CVE-2020-15566 [MEDIUM] CWE-755 GHSA-2v7g-8jvx-2wfc: An issue was discovered in Xen through 4
An issue was discovered in Xen through 4.13.x, allowing guest OS users to cause a host OS crash because of incorrect error handling in event-channel port allocation. The allocation of an event-channel port may fail for multiple reasons: (1) port is already in use, (2) the memory allocation failed, or (3) the port we try to allocate is higher than what is supported by the ABI (e.g., 2L or FIFO) used by the guest or the limit set by an administrator (max_event_channels in xl cfg). Due to the missing error checks, only (1) will be considered an error. All the other cases will provide a valid port and will result in a crash when trying to access the event channel. When the administrator configured a guest to allow more than 1023 event channels, that guest may be able to crash the host. When Xe
OSV
CVE-2020-15566: An issue was discovered in Xen through 4
osv·2020-07-07·CVSS 6.5
CVE-2020-15566 [MEDIUM] CVE-2020-15566: An issue was discovered in Xen through 4
An issue was discovered in Xen through 4.13.x, allowing guest OS users to cause a host OS crash because of incorrect error handling in event-channel port allocation. The allocation of an event-channel port may fail for multiple reasons: (1) port is already in use, (2) the memory allocation failed, or (3) the port we try to allocate is higher than what is supported by the ABI (e.g., 2L or FIFO) used by the guest or the limit set by an administrator (max_event_channels in xl cfg). Due to the missing error checks, only (1) will be considered an error. All the other cases will provide a valid port and will result in a crash when trying to access the event channel. When the administrator configured a guest to allow more than 1023 event channels, that guest may be able to crash the host. When Xe
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2020-15566 xen: incorrect error handling in event channel port allocation leads to DoS (XSA-317) [fedora-all]
bugzilla·2020-07-07·CVSS 6.5
CVE-2020-15566 [MEDIUM] CVE-2020-15566 xen: incorrect error handling in event channel port allocation leads to DoS (XSA-317) [fedora-all]
CVE-2020-15566 xen: incorrect error handling in event channel port allocation leads to DoS (XSA-317) [fedora-all]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of fedora-all.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
NOTE: this issue
Bugzilla
CVE-2020-15566 xen: incorrect error handling in event channel port allocation leads to DoS (XSA-317)
bugzilla·2020-06-26·CVSS 6.5
CVE-2020-15566 [MEDIUM] CVE-2020-15566 xen: incorrect error handling in event channel port allocation leads to DoS (XSA-317)
CVE-2020-15566 xen: incorrect error handling in event channel port allocation leads to DoS (XSA-317)
When the administrator configured a guest to allow more than 1023 event channels, that guest may be able to crash the host. When Xen is out-of-memory, allocation of new event channels will result in crashing the host rather than reporting an error.
Discussion:
Acknowledgments:
Name: the Xen project
---
Statement:
Only Xen versions 4.10 and later are affected by this flaw. The default configuration, when guests are created with xl/libxl, is not vulnerable, because of the default event channel limit (see Mitigation).
---
Mitigation:
The issue can be avoided by reducing the number of event channels available to the guest to no more than 1023. For example, setting `max_event_channels=
http://lists.opensuse.org/opensuse-security-announce/2020-07/msg00024.htmlhttp://lists.opensuse.org/opensuse-security-announce/2020-07/msg00031.htmlhttp://www.openwall.com/lists/oss-security/2020/07/07/2http://xenbits.xen.org/xsa/advisory-317.htmlhttps://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/MXESCOVI7AVRNC7HEAMFM7PMEO6D3AUH/https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/VB3QJJZV23Z2IDYEMIHELWYSQBUEW6JP/https://security.gentoo.org/glsa/202007-02https://www.debian.org/security/2020/dsa-4723http://lists.opensuse.org/opensuse-security-announce/2020-07/msg00024.htmlhttp://lists.opensuse.org/opensuse-security-announce/2020-07/msg00031.htmlhttp://www.openwall.com/lists/oss-security/2020/07/07/2http://xenbits.xen.org/xsa/advisory-317.htmlhttps://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/MXESCOVI7AVRNC7HEAMFM7PMEO6D3AUH/https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/VB3QJJZV23Z2IDYEMIHELWYSQBUEW6JP/https://security.gentoo.org/glsa/202007-02https://www.debian.org/security/2020/dsa-4723
2020-07-07
Published