OESA-2021-1128 (CVE-2020-29443)
Vulnerability from osv_openeuler – Published: 2021-04-07 11:04 – Updated: 2026-08-06 11:04 – Source websiteQEMU is a FAST! processor emulator using dynamic translation to achieve good emulation speed. QEMU has two operating modes: Full system emulation. In this mode, QEMU emulates a full system (for example a PC), including one or several processors and various peripherals. It can be used to launch different Operating Systems without rebooting the PC or to debug system code. User mode emulation. In this mode, QEMU can launch processes compiled for one CPU on another CPU. It can be used to launch the Wine Windows API emulator (https://www.winehq.org) or to ease cross-compilation and cross-debugging. You can refer to https://www.qemu.org for more infortmation.
Security Fix(es):
ide_atapi_cmd_reply_end in hw/ide/atapi.c in QEMU 5.1.0 allows out-of-bounds read access because a buffer index is not validated.(CVE-2020-29443)
An integer overflow issue was found in the vmxnet3 NIC emulator of the QEMU for versions up to v5.2.0. It may occur if a guest was to supply invalid values for rx/tx queue size or other NIC parameters. A privileged guest user may use this flaw to crash the QEMU process on the host resulting in DoS scenario.(CVE-2021-20203)
| URL | Type | |
|---|---|---|
{
"affected": [
{
"ecosystem_specific": {
"aarch64": [
"qemu-img-4.1.0-35.oe1.aarch64.rpm",
"qemu-4.1.0-35.oe1.aarch64.rpm",
"qemu-debuginfo-4.1.0-35.oe1.aarch64.rpm",
"qemu-guest-agent-4.1.0-35.oe1.aarch64.rpm",
"qemu-debugsource-4.1.0-35.oe1.aarch64.rpm",
"qemu-debugsource-4.1.0-37.oe1.aarch64.rpm",
"qemu-debuginfo-4.1.0-37.oe1.aarch64.rpm",
"qemu-img-4.1.0-37.oe1.aarch64.rpm",
"qemu-guest-agent-4.1.0-37.oe1.aarch64.rpm",
"qemu-4.1.0-37.oe1.aarch64.rpm"
],
"noarch": [
"qemu-help-4.1.0-35.oe1.noarch.rpm",
"qemu-help-4.1.0-37.oe1.noarch.rpm"
],
"src": [
"qemu-4.1.0-35.oe1.src.rpm",
"qemu-4.1.0-37.oe1.src.rpm"
],
"x86_64": [
"qemu-debugsource-4.1.0-35.oe1.x86_64.rpm",
"qemu-4.1.0-35.oe1.x86_64.rpm",
"qemu-guest-agent-4.1.0-35.oe1.x86_64.rpm",
"qemu-debuginfo-4.1.0-35.oe1.x86_64.rpm",
"qemu-seabios-4.1.0-35.oe1.x86_64.rpm",
"qemu-img-4.1.0-35.oe1.x86_64.rpm",
"qemu-4.1.0-37.oe1.x86_64.rpm",
"qemu-debuginfo-4.1.0-37.oe1.x86_64.rpm",
"qemu-img-4.1.0-37.oe1.x86_64.rpm",
"qemu-guest-agent-4.1.0-37.oe1.x86_64.rpm",
"qemu-seabios-4.1.0-37.oe1.x86_64.rpm",
"qemu-debugsource-4.1.0-37.oe1.x86_64.rpm"
]
},
"package": {
"ecosystem": "openEuler:20.03-LTS",
"name": "qemu",
"purl": "pkg:rpm/openEuler/qemu\u0026distro=openEuler-20.03-LTS"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "4.1.0-37.oe1"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"ecosystem_specific": {
"aarch64": [
"qemu-debugsource-4.1.0-37.oe1.aarch64.rpm",
"qemu-debuginfo-4.1.0-37.oe1.aarch64.rpm",
"qemu-img-4.1.0-37.oe1.aarch64.rpm",
"qemu-guest-agent-4.1.0-37.oe1.aarch64.rpm",
"qemu-4.1.0-37.oe1.aarch64.rpm"
],
"noarch": [
"qemu-help-4.1.0-37.oe1.noarch.rpm"
],
"src": [
"qemu-4.1.0-37.oe1.src.rpm"
],
"x86_64": [
"qemu-4.1.0-37.oe1.x86_64.rpm",
"qemu-debuginfo-4.1.0-37.oe1.x86_64.rpm",
"qemu-img-4.1.0-37.oe1.x86_64.rpm",
"qemu-guest-agent-4.1.0-37.oe1.x86_64.rpm",
"qemu-seabios-4.1.0-37.oe1.x86_64.rpm",
"qemu-debugsource-4.1.0-37.oe1.x86_64.rpm"
]
},
"package": {
"ecosystem": "openEuler:20.03-LTS-SP1",
"name": "qemu",
"purl": "pkg:rpm/openEuler/qemu\u0026distro=openEuler-20.03-LTS-SP1"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "4.1.0-37.oe1"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"database_specific": {
"severity": "Medium"
},
"details": "QEMU is a FAST! processor emulator using dynamic translation to achieve good emulation speed. QEMU has two operating modes: Full system emulation. In this mode, QEMU emulates a full system (for example a PC), including one or several processors and various peripherals. It can be used to launch different Operating Systems without rebooting the PC or to debug system code. User mode emulation. In this mode, QEMU can launch processes compiled for one CPU on another CPU. It can be used to launch the Wine Windows API emulator (https://www.winehq.org) or to ease cross-compilation and cross-debugging. You can refer to https://www.qemu.org for more infortmation.\r\n\r\nSecurity Fix(es):\r\n\r\nide_atapi_cmd_reply_end in hw/ide/atapi.c in QEMU 5.1.0 allows out-of-bounds read access because a buffer index is not validated.(CVE-2020-29443)\r\n\r\nAn integer overflow issue was found in the vmxnet3 NIC emulator of the QEMU for versions up to v5.2.0. It may occur if a guest was to supply invalid values for rx/tx queue size or other NIC parameters. A privileged guest user may use this flaw to crash the QEMU process on the host resulting in DoS scenario.(CVE-2021-20203)",
"id": "OESA-2021-1128",
"modified": "2026-08-06T11:04:22Z",
"published": "2021-04-07T11:04:22Z",
"references": [
{
"type": "ADVISORY",
"url": "https://openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2021-1128"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2020-29443"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2021-20203"
}
],
"schema_version": "1.7.2",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H",
"type": "CVSS_V3"
}
],
"summary": "qemu security update",
"upstream": [
"CVE-2020-29443",
"CVE-2021-20203"
]
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.