CVE-2020-29484
An issue was discovered in Xen through 4.14.x. When a Xenstore watch fires, the xenstore client...
An issue was discovered in Xen through 4.14.x. When a Xenstore watch fires, the xenstore client that registered the watch will receive a Xenstore message containing the path of the modified Xenstore entry that triggered the watch, and the tag that was specified when registering the watch. Any communication with xenstored is done via Xenstore messages, consisting of a message header and the payload. The payload length is limited to 4096 bytes. Any request to xenstored resulting in a response with a payload longer than 4096 bytes will result in an error. When registering a watch, the payload length limit applies to the combined length of the watched path and the specified tag. Because watches for a specific path are also triggered for all nodes below that path, the payload of a watch event message can be longer than the payload needed to register the watch. A malicious guest that registers a watch using a very large tag (i.e., with a registration operation payload length close to the 4096 byte limit) can cause the generation of watch events with a payload length larger than 4096 bytes, by writing to Xenstore entries below the watched path. This will result in an error condition in xenstored. This error can result in a NULL pointer dereference, leading to a crash of xenstored. A malicious guest administrator can cause xenstored to crash, leading to a denial of service. Following a xenstored crash, domains may continue to run, but management operations will be impossible. Only C xenstored is affected, oxenstored is not affected.
Attack profile
How easy it is to exploit
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- High
- User interaction
- None
What an attacker can affect
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Exploit likelihood
What each source reports
NVD Score used
An issue was discovered in Xen through 4.14.x. When a Xenstore watch fires, the xenstore client that registered the watch will receive a Xenstore message containing the path of the modified Xenstore entry that triggered the watch, and the tag that was specified when registering the watch. Any communication with xenstored is done via Xenstore messages, consisting of a message header and the payload. The payload length is limited to 4096 bytes. Any request to xenstored resulting in a response with a payload longer than 4096 bytes will result in an error. When registering a watch, the payload length limit applies to the combined length of the watched path and the specified tag. Because watches for a specific path are also triggered for all nodes below that path, the payload of a watch event message can be longer than the payload needed to register the watch. A malicious guest that registers a watch using a very large tag (i.e., with a registration operation payload length close to the 4096 byte limit) can cause the generation of watch events with a payload length larger than 4096 bytes, by writing to Xenstore entries below the watched path. This will result in an error condition in xenstored. This error can result in a NULL pointer dereference, leading to a crash of xenstored. A malicious guest administrator can cause xenstored to crash, leading to a denial of service. Following a xenstored crash, domains may continue to run, but management operations will be impossible. Only C xenstored is affected, oxenstored is not affected.
- Record
CVE-2020-29484- CVSS 3.1
- 6.0 Medium
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:N/I:N/A:H - CVSS 2.0
- 4.9 Medium
AV:L/AC:L/Au:N/C:N/I:N/A:C - Weakness
- CWE-476
- Updated
- 2026-11-02
CVE List No score
An issue was discovered in Xen through 4.14.x. When a Xenstore watch fires, the xenstore client that registered the watch will receive a Xenstore message containing the path of the modified Xenstore entry that triggered the watch, and the tag that was specified when registering the watch. Any communication with xenstored is done via Xenstore messages, consisting of a message header and the payload. The payload length is limited to 4096 bytes. Any request to xenstored resulting in a response with a payload longer than 4096 bytes will result in an error. When registering a watch, the payload length limit applies to the combined length of the watched path and the specified tag. Because watches for a specific path are also triggered for all nodes below that path, the payload of a watch event message can be longer than the payload needed to register the watch. A malicious guest that registers a watch using a very large tag (i.e., with a registration operation payload length close to the 4096 byte limit) can cause the generation of watch events with a payload length larger than 4096 bytes, by writing to Xenstore entries below the watched path. This will result in an error condition in xenstored. This error can result in a NULL pointer dereference, leading to a crash of xenstored. A malicious guest administrator can cause xenstored to crash, leading to a denial of service. Following a xenstored crash, domains may continue to run, but management operations will be impossible. Only C xenstored is affected, oxenstored is not affected.
- Record
CVE-2020-29484- Updated
- 2026-11-02
EUVDEUVD-2020-21852 No score
An issue was discovered in Xen through 4.14.x. When a Xenstore watch fires, the xenstore client that registered the watch will receive a Xenstore message containing the path of the modified Xenstore entry that triggered the watch, and the tag that was specified when registering the watch. Any communication with xenstored is done via Xenstore messages, consisting of a message header and the payload. The payload length is limited to 4096 bytes. Any request to xenstored resulting in a response with a payload longer than 4096 bytes will result in an error. When registering a watch, the payload length limit applies to the combined length of the watched path and the specified tag. Because watches for a specific path are also triggered for all nodes below that path, the payload of a watch event message can be longer than the payload needed to register the watch. A malicious guest that registers a watch using a very large tag (i.e., with a registration operation payload length close to the 4096 byte limit) can cause the generation of watch events with a payload length larger than 4096 bytes, by writing to Xenstore entries below the watched path. This will result in an error condition in xenstored. This error can result in a NULL pointer dereference, leading to a crash of xenstored. A malicious guest administrator can cause xenstored to crash, leading to a denial of service. Following a xenstored crash, domains may continue to run, but management operations will be impossible. Only C xenstored is affected, oxenstored is not affected.
- Record
EUVD-2020-21852- Updated
- 2026-11-03
GitHub AdvisoriesGHSA-58pp-88x2-wf7f No score
An issue was discovered in Xen through 4.14.x. When a Xenstore watch fires, the xenstore client...
An issue was discovered in Xen through 4.14.x. When a Xenstore watch fires, the xenstore client that registered the watch will receive a Xenstore message containing the path of the modified Xenstore entry that triggered the watch, and the tag that was specified when registering the watch. Any communication with xenstored is done via Xenstore messages, consisting of a message header and the payload. The payload length is limited to 4096 bytes. Any request to xenstored resulting in a response with a payload longer than 4096 bytes will result in an error. When registering a watch, the payload length limit applies to the combined length of the watched path and the specified tag. Because watches for a specific path are also triggered for all nodes below that path, the payload of a watch event message can be longer than the payload needed to register the watch. A malicious guest that registers a watch using a very large tag (i.e., with a registration operation payload length close to the 4096 byte limit) can cause the generation of watch events with a payload length larger than 4096 bytes, by writing to Xenstore entries below the watched path. This will result in an error condition in xenstored. This error can result in a NULL pointer dereference, leading to a crash of xenstored. A malicious guest administrator can cause xenstored to crash, leading to a denial of service. Following a xenstored crash, domains may continue to run, but management operations will be impossible. Only C xenstored is affected, oxenstored is not affected.
- Record
GHSA-58pp-88x2-wf7f- Weakness
- CWE-476
- Updated
- 2026-11-02
OSVALPINE-CVE-2020-29484
An issue was discovered in Xen through 4.14.x. When a Xenstore watch fires, the xenstore client that registered the watch will receive a Xenstore message containing the path of the modified Xenstore entry that triggered the watch, and the tag that was specified when registering the watch. Any communication with xenstored is done via Xenstore messages, consisting of a message header and the payload. The payload length is limited to 4096 bytes. Any request to xenstored resulting in a response with a payload longer than 4096 bytes will result in an error. When registering a watch, the payload length limit applies to the combined length of the watched path and the specified tag. Because watches for a specific path are also triggered for all nodes below that path, the payload of a watch event message can be longer than the payload needed to register the watch. A malicious guest that registers a watch using a very large tag (i.e., with a registration operation payload length close to the 4096 byte limit) can cause the generation of watch events with a payload length larger than 4096 bytes, by writing to Xenstore entries below the watched path. This will result in an error condition in xenstored. This error can result in a NULL pointer dereference, leading to a crash of xenstored. A malicious guest administrator can cause xenstored to crash, leading to a denial of service. Following a xenstored crash, domains may continue to run, but management operations will be impossible. Only C xenstored is affected, oxenstored is not affected.
- Record
ALPINE-CVE-2020-29484- CVSS 3.1
- 6.0 Medium
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:N/I:N/A:H - Updated
- 2026-11-02
OSV
An issue was discovered in Xen through 4.14.x. When a Xenstore watch fires, the xenstore client that registered the watch will receive a Xenstore message containing the path of the modified Xenstore entry that triggered the watch, and the tag that was specified when registering the watch. Any communication with xenstored is done via Xenstore messages, consisting of a message header and the payload. The payload length is limited to 4096 bytes. Any request to xenstored resulting in a response with a payload longer than 4096 bytes will result in an error. When registering a watch, the payload length limit applies to the combined length of the watched path and the specified tag. Because watches for a specific path are also triggered for all nodes below that path, the payload of a watch event message can be longer than the payload needed to register the watch. A malicious guest that registers a watch using a very large tag (i.e., with a registration operation payload length close to the 4096 byte limit) can cause the generation of watch events with a payload length larger than 4096 bytes, by writing to Xenstore entries below the watched path. This will result in an error condition in xenstored. This error can result in a NULL pointer dereference, leading to a crash of xenstored. A malicious guest administrator can cause xenstored to crash, leading to a denial of service. Following a xenstored crash, domains may continue to run, but management operations will be impossible. Only C xenstored is affected, oxenstored is not affected.
- Record
CVE-2020-29484- CVSS 3.1
- 6.0 Medium
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:N/I:N/A:H - Updated
- 2026-11-02
Show 13 moreShow less
OSVDEBIAN-CVE-2020-29484
An issue was discovered in Xen through 4.14.x. When a Xenstore watch fires, the xenstore client that registered the watch will receive a Xenstore message containing the path of the modified Xenstore entry that triggered the watch, and the tag that was specified when registering the watch. Any communication with xenstored is done via Xenstore messages, consisting of a message header and the payload. The payload length is limited to 4096 bytes. Any request to xenstored resulting in a response with a payload longer than 4096 bytes will result in an error. When registering a watch, the payload length limit applies to the combined length of the watched path and the specified tag. Because watches for a specific path are also triggered for all nodes below that path, the payload of a watch event message can be longer than the payload needed to register the watch. A malicious guest that registers a watch using a very large tag (i.e., with a registration operation payload length close to the 4096 byte limit) can cause the generation of watch events with a payload length larger than 4096 bytes, by writing to Xenstore entries below the watched path. This will result in an error condition in xenstored. This error can result in a NULL pointer dereference, leading to a crash of xenstored. A malicious guest administrator can cause xenstored to crash, leading to a denial of service. Following a xenstored crash, domains may continue to run, but management operations will be impossible. Only C xenstored is affected, oxenstored is not affected.
- Record
DEBIAN-CVE-2020-29484- CVSS 3.1
- 6.0 Medium
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:N/I:N/A:H - Updated
- 2026-11-02
OSVUBUNTU-CVE-2020-29484
An issue was discovered in Xen through 4.14.x. When a Xenstore watch fires, the xenstore client that registered the watch will receive a Xenstore message containing the path of the modified Xenstore entry that triggered the watch, and the tag that was specified when registering the watch. Any communication with xenstored is done via Xenstore messages, consisting of a message header and the payload. The payload length is limited to 4096 bytes. Any request to xenstored resulting in a response with a payload longer than 4096 bytes will result in an error. When registering a watch, the payload length limit applies to the combined length of the watched path and the specified tag. Because watches for a specific path are also triggered for all nodes below that path, the payload of a watch event message can be longer than the payload needed to register the watch. A malicious guest that registers a watch using a very large tag (i.e., with a registration operation payload length close to the 4096 byte limit) can cause the generation of watch events with a payload length larger than 4096 bytes, by writing to Xenstore entries below the watched path. This will result in an error condition in xenstored. This error can result in a NULL pointer dereference, leading to a crash of xenstored. A malicious guest administrator can cause xenstored to crash, leading to a denial of service. Following a xenstored crash, domains may continue to run, but management operations will be impossible. Only C xenstored is affected, oxenstored is not affected.
- Record
UBUNTU-CVE-2020-29484- CVSS 3.1
- 6.0 Medium
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:N/I:N/A:H - Updated
- 2026-11-02
OSVopenSUSE-SU-2020:2313-1 No score
Security update for xen
This update for xen fixes the following issues:
- CVE-2020-29480: Fixed an issue which could have allowed leak of non-sensitive data to administrator guests (bsc#117949 XSA-115).
- CVE-2020-29481: Fixed an issue which could have allowd to new domains to inherit existing node permissions (bsc#1179498 XSA-322).
- CVE-2020-29483: Fixed an issue where guests could disturb domain cleanup (bsc#1179502 XSA-325).
- CVE-2020-29484: Fixed an issue where guests could crash xenstored via watchs (bsc#1179501 XSA-324).
- CVE-2020-29566: Fixed an undue recursion in x86 HVM context switch code (bsc#1179506 XSA-348).
- CVE-2020-29570: Fixed an issue where FIFO event channels control block related ordering (bsc#1179514 XSA-358).
- CVE-2020-29571: Fixed an issue where FIFO event channels control structure ordering (bsc#1179516 XSA-359).
- Fixed an issue where dump-core shows missing nr_pages during core (bsc#1176782).
- Multiple other bugs (bsc#1027519)
This update was imported from the SUSE:SLE-15-SP1:Update update project.
- Record
openSUSE-SU-2020:2313-1- Updated
- 2026-11-02
OSVopenSUSE-SU-2020:2331-1 No score
Security update for xen
This update for xen fixes the following issues:
- CVE-2020-29480: Fixed an issue which could have allowed leak of non-sensitive data to administrator guests (bsc#117949 XSA-115).
- CVE-2020-29481: Fixed an issue which could have allowd to new domains to inherit existing node permissions (bsc#1179498 XSA-322).
- CVE-2020-29483: Fixed an issue where guests could disturb domain cleanup (bsc#1179502 XSA-325).
- CVE-2020-29484: Fixed an issue where guests could crash xenstored via watchs (bsc#1179501 XSA-324).
- CVE-2020-29566: Fixed an undue recursion in x86 HVM context switch code (bsc#1179506 XSA-348).
- CVE-2020-29570: Fixed an issue where FIFO event channels control block related ordering (bsc#1179514 XSA-358).
- CVE-2020-29571: Fixed an issue where FIFO event channels control structure ordering (bsc#1179516 XSA-359).
- Fixed an issue where dump-core shows missing nr_pages during core (bsc#1176782).
- Multiple other bugs (bsc#1027519)
This update was imported from the SUSE:SLE-15-SP2:Update update project.
- Record
openSUSE-SU-2020:2331-1- Updated
- 2026-11-02
OSVopenSUSE-SU-2024:11520-1 No score
xen-4.15.1_01-1.2 on GA media
These are all security issues fixed in the xen-4.15.1_01-1.2 package on the GA media of openSUSE Tumbleweed.
- Record
openSUSE-SU-2024:11520-1- Updated
- 2026-11-02
OSVSUSE-SU-2020:14578-1 No score
Security update for xen
This update for xen fixes the following issues:
- CVE-2020-29480: Fixed an issue which could have allowed leak of non-sensitive data to administrator guests (bsc#117949 XSA-115).
- CVE-2020-29481: Fixed an issue which could have allowd to new domains to inherit existing node permissions (bsc#1179498 XSA-322).
- CVE-2020-29483: Fixed an issue where guests could disturb domain cleanup (bsc#1179502 XSA-325).
- CVE-2020-29484: Fixed an issue where guests could crash xenstored via watchs (bsc#1179501 XSA-324).
- CVE-2020-29566: Fixed an undue recursion in x86 HVM context switch code (bsc#1179506 XSA-348).
- CVE-2020-29570: Fixed an issue where FIFO event channels control block related ordering (bsc#1179514 XSA-358).
- CVE-2020-29571: Fixed an issue where FIFO event channels control structure ordering (bsc#1179516 XSA-359).
- CVE-2020-29130: Fixed an out-of-bounds access while processing ARP packets (bsc#1179477).
- Record
SUSE-SU-2020:14578-1- Updated
- 2026-11-02
OSVSUSE-SU-2020:3880-1 No score
Security update for xen
This update for xen fixes the following issues:
- CVE-2020-29480: Fixed an issue which could have allowed leak of non-sensitive data to administrator guests (bsc#117949 XSA-115).
- CVE-2020-29481: Fixed an issue which could have allowd to new domains to inherit existing node permissions (bsc#1179498 XSA-322).
- CVE-2020-29483: Fixed an issue where guests could disturb domain cleanup (bsc#1179502 XSA-325).
- CVE-2020-29484: Fixed an issue where guests could crash xenstored via watchs (bsc#1179501 XSA-324).
- CVE-2020-29566: Fixed an undue recursion in x86 HVM context switch code (bsc#1179506 XSA-348).
- CVE-2020-29570: Fixed an issue where FIFO event channels control block related ordering (bsc#1179514 XSA-358).
- CVE-2020-29571: Fixed an issue where FIFO event channels control structure ordering (bsc#1179516 XSA-359).
- CVE-2020-29130: Fixed an out-of-bounds access while processing ARP packets (bsc#1179477).
- Fixed an issue where dump-core shows missing nr_pages during core (bsc#1176782).
- Multiple other bugs (bsc#1027519)
- Record
SUSE-SU-2020:3880-1- Updated
- 2026-11-02
OSVSUSE-SU-2020:3881-1 No score
Security update for xen
This update for xen fixes the following issues:
- CVE-2020-29480: Fixed an issue which could have allowed leak of non-sensitive data to administrator guests (bsc#117949 XSA-115).
- CVE-2020-29481: Fixed an issue which could have allowd to new domains to inherit existing node permissions (bsc#1179498 XSA-322).
- CVE-2020-29483: Fixed an issue where guests could disturb domain cleanup (bsc#1179502 XSA-325).
- CVE-2020-29484: Fixed an issue where guests could crash xenstored via watchs (bsc#1179501 XSA-324).
- CVE-2020-29566: Fixed an undue recursion in x86 HVM context switch code (bsc#1179506 XSA-348).
- CVE-2020-29570: Fixed an issue where FIFO event channels control block related ordering (bsc#1179514 XSA-358).
- CVE-2020-29571: Fixed an issue where FIFO event channels control structure ordering (bsc#1179516 XSA-359).
- Fixed an issue where dump-core shows missing nr_pages during core (bsc#1176782).
- Multiple other bugs (bsc#1027519)
- Record
SUSE-SU-2020:3881-1- Updated
- 2026-11-02
OSVSUSE-SU-2020:3913-1 No score
Security update for xen
This update for xen fixes the following issues:
- CVE-2020-29480: Fixed an issue which could have allowed leak of non-sensitive data to administrator guests (bsc#117949 XSA-115).
- CVE-2020-29481: Fixed an issue which could have allowd to new domains to inherit existing node permissions (bsc#1179498 XSA-322).
- CVE-2020-29483: Fixed an issue where guests could disturb domain cleanup (bsc#1179502 XSA-325).
- CVE-2020-29484: Fixed an issue where guests could crash xenstored via watchs (bsc#1179501 XSA-324).
- CVE-2020-29566: Fixed an undue recursion in x86 HVM context switch code (bsc#1179506 XSA-348).
- CVE-2020-29570: Fixed an issue where FIFO event channels control block related ordering (bsc#1179514 XSA-358).
- CVE-2020-29571: Fixed an issue where FIFO event channels control structure ordering (bsc#1179516 XSA-359).
- CVE-2020-29130: Fixed an out-of-bounds access while processing ARP packets (bsc#1179477).
- Fixed an issue where dump-core shows missing nr_pages during core (bsc#1176782).
- Multiple other bugs (bsc#1027519)
- Record
SUSE-SU-2020:3913-1- Updated
- 2026-11-02
OSVSUSE-SU-2020:3914-1 No score
Security update for xen
This update for xen fixes the following issues:
- CVE-2020-29480: Fixed an issue which could have allowed leak of non-sensitive data to administrator guests (bsc#117949 XSA-115).
- CVE-2020-29481: Fixed an issue which could have allowd to new domains to inherit existing node permissions (bsc#1179498 XSA-322).
- CVE-2020-29483: Fixed an issue where guests could disturb domain cleanup (bsc#1179502 XSA-325).
- CVE-2020-29484: Fixed an issue where guests could crash xenstored via watchs (bsc#1179501 XSA-324).
- CVE-2020-29566: Fixed an undue recursion in x86 HVM context switch code (bsc#1179506 XSA-348).
- CVE-2020-29570: Fixed an issue where FIFO event channels control block related ordering (bsc#1179514 XSA-358).
- CVE-2020-29571: Fixed an issue where FIFO event channels control structure ordering (bsc#1179516 XSA-359).
- CVE-2020-29130: Fixed an out-of-bounds access while processing ARP packets (bsc#1179477).
- Fixed an issue where dump-core shows missing nr_pages during core (bsc#1176782).
- Multiple other bugs (bsc#1027519)
- Record
SUSE-SU-2020:3914-1- Updated
- 2026-11-02
OSVSUSE-SU-2020:3915-1 No score
Security update for xen
This update for xen fixes the following issues:
- CVE-2020-29480: Fixed an issue which could have allowed leak of non-sensitive data to administrator guests (bsc#117949 XSA-115).
- CVE-2020-29481: Fixed an issue which could have allowd to new domains to inherit existing node permissions (bsc#1179498 XSA-322).
- CVE-2020-29483: Fixed an issue where guests could disturb domain cleanup (bsc#1179502 XSA-325).
- CVE-2020-29484: Fixed an issue where guests could crash xenstored via watchs (bsc#1179501 XSA-324).
- CVE-2020-29566: Fixed an undue recursion in x86 HVM context switch code (bsc#1179506 XSA-348).
- CVE-2020-29570: Fixed an issue where FIFO event channels control block related ordering (bsc#1179514 XSA-358).
- CVE-2020-29571: Fixed an issue where FIFO event channels control structure ordering (bsc#1179516 XSA-359).
- Fixed an issue where dump-core shows missing nr_pages during core (bsc#1176782).
- Multiple other bugs (bsc#1027519)
- Record
SUSE-SU-2020:3915-1- Updated
- 2026-11-02
OSVSUSE-SU-2020:3916-1 No score
Security update for xen
This update for xen fixes the following issues:
- CVE-2020-29480: Fixed an issue which could have allowed leak of non-sensitive data to administrator guests (bsc#117949 XSA-115).
- CVE-2020-29481: Fixed an issue which could have allowd to new domains to inherit existing node permissions (bsc#1179498 XSA-322).
- CVE-2020-29483: Fixed an issue where guests could disturb domain cleanup (bsc#1179502 XSA-325).
- CVE-2020-29484: Fixed an issue where guests could crash xenstored via watchs (bsc#1179501 XSA-324).
- CVE-2020-29566: Fixed an undue recursion in x86 HVM context switch code (bsc#1179506 XSA-348).
- CVE-2020-29570: Fixed an issue where FIFO event channels control block related ordering (bsc#1179514 XSA-358).
- CVE-2020-29571: Fixed an issue where FIFO event channels control structure ordering (bsc#1179516 XSA-359).
- Fixed an issue where dump-core shows missing nr_pages during core (bsc#1176782).
- Multiple other bugs (bsc#1027519)
- Record
SUSE-SU-2020:3916-1- Updated
- 2026-11-02
OSVSUSE-SU-2020:3945-1 No score
Security update for xen
This update for xen fixes the following issues:
- CVE-2020-29480: Fixed an issue which could have allowed leak of non-sensitive data to administrator guests (bsc#117949 XSA-115).
- CVE-2020-29481: Fixed an issue which could have allowd to new domains to inherit existing node permissions (bsc#1179498 XSA-322).
- CVE-2020-29483: Fixed an issue where guests could disturb domain cleanup (bsc#1179502 XSA-325).
- CVE-2020-29484: Fixed an issue where guests could crash xenstored via watchs (bsc#1179501 XSA-324).
- CVE-2020-29566: Fixed an undue recursion in x86 HVM context switch code (bsc#1179506 XSA-348).
- CVE-2020-29570: Fixed an issue where FIFO event channels control block related ordering (bsc#1179514 XSA-358).
- CVE-2020-29571: Fixed an issue where FIFO event channels control structure ordering (bsc#1179516 XSA-359).
- CVE-2020-29130: Fixed an out-of-bounds access while processing ARP packets (bsc#1179477).
- Fixed an issue where dump-core shows missing nr_pages during core (bsc#1176782).
- Multiple other bugs (bsc#1027519)
- Record
SUSE-SU-2020:3945-1- Updated
- 2026-11-02
Affected products
Affected packages
| Package | Affected | Fixed |
|---|---|---|
xenAlpine:v3.11 |
before 4.13.2-r3 | 4.13.2-r3 |
xenAlpine:v3.12 |
before 4.13.2-r3 | 4.13.2-r3 |
xenAlpine:v3.13 |
before 4.14.1-r0 | 4.14.1-r0 |
xenAlpine:v3.14 |
before 4.14.1-r0 | 4.14.1-r0 |
xenAlpine:v3.15 |
before 4.14.1-r0 | 4.14.1-r0 |
xenAlpine:v3.16 |
before 4.14.1-r0 | 4.14.1-r0 |
xenAlpine:v3.17 |
before 4.14.1-r0 | 4.14.1-r0 |
xenAlpine:v3.18 |
before 4.14.1-r0 | 4.14.1-r0 |
xenAlpine:v3.19 |
before 4.14.1-r0 | 4.14.1-r0 |
xenAlpine:v3.20 |
before 4.14.1-r0 | 4.14.1-r0 |
Show 40 moreShow less
| Package | Affected | Fixed |
|---|---|---|
xenAlpine:v3.21 |
before 4.14.1-r0 | 4.14.1-r0 |
xenAlpine:v3.22 |
before 4.14.1-r0 | 4.14.1-r0 |
xenAlpine:v3.23 |
before 4.14.1-r0 | 4.14.1-r0 |
xenAlpine:v3.24 |
before 4.14.1-r0 | 4.14.1-r0 |
xenDebian:12 |
before 4.14.0+88-g1d1d1f5391-1 | 4.14.0+88-g1d1d1f5391-1 |
xenDebian:13 |
before 4.14.0+88-g1d1d1f5391-1 | 4.14.0+88-g1d1d1f5391-1 |
xenDebian:14 |
before 4.14.0+88-g1d1d1f5391-1 | 4.14.0+88-g1d1d1f5391-1 |
xenDebian:10 From an advisory covering 11 CVEs |
before 4.11.4+57-g41a822c392-2, plus listed versions 4.11.1+92-g6c33308a8d-24.11.3+24-g14b62ab3e5-14.11.3+24-g14b62ab3e5-1~deb10u14.11.4+24-gddaaccbbab-14.11.4+24-gddaaccbbab-1~deb10u14.11.4+37-g3263f257ca-14.11.4+57-g41a822c392-14.11.4-1 |
4.11.4+57-g41a822c392-2 |
xenSUSE:Linux Enterprise Server 11 SP4-LTSS From an advisory covering 8 CVEs |
before 4.4.4_48-61.61.1 | 4.4.4_48-61.61.1 |
xenSUSE:Linux Enterprise Software Development Kit 12 SP5 From an advisory covering 9 CVEs |
before 4.12.4_06-3.36.1 | 4.12.4_06-3.36.1 |
xenSUSE:Linux Enterprise Server 12 SP5 From an advisory covering 9 CVEs |
before 4.12.4_06-3.36.1 | 4.12.4_06-3.36.1 |
xenSUSE:Linux Enterprise Server for SAP Applications 12 SP5 From an advisory covering 9 CVEs |
before 4.12.4_06-3.36.1 | 4.12.4_06-3.36.1 |
xenSUSE:Linux Enterprise Module for Basesystem 15 SP1 From an advisory covering 7 CVEs |
before 4.12.4_06-3.40.1 | 4.12.4_06-3.40.1 |
xenSUSE:Linux Enterprise Module for Server Applications 15 SP1 From an advisory covering 7 CVEs |
before 4.12.4_06-3.40.1 | 4.12.4_06-3.40.1 |
xenSUSE:OpenStack Cloud 7 From an advisory covering 8 CVEs |
before 4.7.6_14-43.73.1 | 4.7.6_14-43.73.1 |
xenSUSE:Linux Enterprise Server for SAP Applications 12 SP2 From an advisory covering 8 CVEs |
before 4.7.6_14-43.73.1 | 4.7.6_14-43.73.1 |
xenSUSE:Linux Enterprise Server 12 SP2-LTSS From an advisory covering 8 CVEs |
before 4.7.6_14-43.73.1 | 4.7.6_14-43.73.1 |
xenSUSE:Linux Enterprise Server 12 SP2-BCL From an advisory covering 8 CVEs |
before 4.7.6_14-43.73.1 | 4.7.6_14-43.73.1 |
xenSUSE:OpenStack Cloud 9 From an advisory covering 8 CVEs |
before 4.11.4_16-2.48.1 | 4.11.4_16-2.48.1 |
xenSUSE:OpenStack Cloud Crowbar 9 From an advisory covering 8 CVEs |
before 4.11.4_16-2.48.1 | 4.11.4_16-2.48.1 |
xenSUSE:Linux Enterprise Server for SAP Applications 12 SP4 From an advisory covering 8 CVEs |
before 4.11.4_16-2.48.1 | 4.11.4_16-2.48.1 |
xenSUSE:Linux Enterprise Server 12 SP4-LTSS From an advisory covering 8 CVEs |
before 4.11.4_16-2.48.1 | 4.11.4_16-2.48.1 |
xenSUSE:Linux Enterprise Module for Basesystem 15 SP2 From an advisory covering 7 CVEs |
before 4.13.2_06-3.22.1 | 4.13.2_06-3.22.1 |
xenSUSE:Linux Enterprise Module for Server Applications 15 SP2 From an advisory covering 7 CVEs |
before 4.13.2_06-3.22.1 | 4.13.2_06-3.22.1 |
xenSUSE:Linux Enterprise High Performance Computing 15-ESPOS From an advisory covering 7 CVEs |
before 4.10.4_24-3.53.1 | 4.10.4_24-3.53.1 |
xenSUSE:Linux Enterprise High Performance Computing 15-LTSS From an advisory covering 7 CVEs |
before 4.10.4_24-3.53.1 | 4.10.4_24-3.53.1 |
xenSUSE:Linux Enterprise Server for SAP Applications 15 From an advisory covering 7 CVEs |
before 4.10.4_24-3.53.1 | 4.10.4_24-3.53.1 |
xenSUSE:HPE Helion OpenStack 8 From an advisory covering 8 CVEs |
before 4.9.4_16-3.80.1 | 4.9.4_16-3.80.1 |
xenSUSE:OpenStack Cloud 8 From an advisory covering 8 CVEs |
before 4.9.4_16-3.80.1 | 4.9.4_16-3.80.1 |
xenSUSE:OpenStack Cloud Crowbar 8 From an advisory covering 8 CVEs |
before 4.9.4_16-3.80.1 | 4.9.4_16-3.80.1 |
xenSUSE:Linux Enterprise Server for SAP Applications 12 SP3 From an advisory covering 8 CVEs |
before 4.9.4_16-3.80.1 | 4.9.4_16-3.80.1 |
xenSUSE:Linux Enterprise Server 12 SP3-LTSS From an advisory covering 8 CVEs |
before 4.9.4_16-3.80.1 | 4.9.4_16-3.80.1 |
xenSUSE:Linux Enterprise Server 12 SP3-BCL From an advisory covering 8 CVEs |
before 4.9.4_16-3.80.1 | 4.9.4_16-3.80.1 |
xenSUSE:Enterprise Storage 5 From an advisory covering 8 CVEs |
before 4.9.4_16-3.80.1 | 4.9.4_16-3.80.1 |
xenUbuntu:16.04:LTS |
All versions, plus listed versions 4.5.1-0ubuntu14.5.1-0ubuntu24.6.0-1ubuntu14.6.0-1ubuntu24.6.0-1ubuntu4 Show 7 moreShow less4.6.0-1ubuntu4.14.6.0-1ubuntu4.24.6.0-1ubuntu4.34.6.5-0ubuntu14.6.5-0ubuntu1.14.6.5-0ubuntu1.24.6.5-0ubuntu1.4 |
None known |
xenUbuntu:18.04:LTS |
All versions, plus listed versions 4.9.0-0ubuntu34.9.0-0ubuntu44.9.2-0ubuntu1 |
None known |
xenUbuntu:20.04:LTS |
All versions, plus listed versions 4.9.2-0ubuntu24.9.2-0ubuntu64.9.2-0ubuntu74.11.3+24-g14b62ab3e5-1ubuntu14.11.3+24-g14b62ab3e5-1ubuntu24.11.3+24-g14b62ab3e5-1ubuntu2.24.11.3+24-g14b62ab3e5-1ubuntu2.3 |
None known |
xenopenSUSE:Leap 15.1 From an advisory covering 7 CVEs |
before 4.12.4_06-lp151.2.36.1 | 4.12.4_06-lp151.2.36.1 |
xenopenSUSE:Leap 15.2 From an advisory covering 7 CVEs |
before 4.13.2_06-lp152.2.21.1 | 4.13.2_06-lp152.2.21.1 |
xenopenSUSE:Tumbleweed From an advisory covering 93 CVEs |
before 4.15.1_01-1.2 | 4.15.1_01-1.2 |
History
| Recorded | Changed | Sources |
|---|---|---|
| affected, facts | ||
| aliases | EUVD | |
| first indexed | CVE List, GitHub Advisories, NVD, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2020-29484 is a medium vulnerability (CVSS 6.0) in Xen, published December 15, 2020. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.39%, the 33rd percentile. Fixed in xen 4.13.2-r3.
References
xenbits.xenproject.org/xsa/advisory-324.txt
debian.org/security/2020/dsa-4812
lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/OBLV6L6Q24PPQ2CRFXDX4Q76KU776GKI
nvd.nist.gov/vuln/detail/CVE-2020-29484
Show 123 moreShow less
github.com/advisories/GHSA-58pp-88x2-wf7f
security.alpinelinux.org/vuln/CVE-2020-29484
security-tracker.debian.org/tracker/CVE-2020-29484
suse.com/support/update/announcement/2020/suse-su-202014578-1
bugzilla.suse.com/1179477
ubuntu.com/security/CVE-2020-29484
xenbits.xen.org/xsa/advisory-324.html
cve.org/CVERecord?id=CVE-2020-29484
lists.opensuse.org/archives/list/[email protected]/thread/ORUQM2NUGI7GTGQ4QQYAXYCCBGXOCR55