oesa-2021-1012
Vulnerability from osv_openeuler
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\n Security Fix(es):\r\n\r\n A flaw was found in the memory management API of QEMU during the initialization of a memory region cache. This issue could lead to an out-of-bounds write access to the MSI-X table while performing MMIO operations. A guest user may abuse this flaw to crash the QEMU process on the host, resulting in a denial of service. This flaw affects QEMU versions prior to 5.2.0.(CVE-2020-27821)\r\n\r\n
| URL | Type | |
|---|---|---|
{
"affected": [
{
"ecosystem_specific": {
"aarch64": [
"qemu-debugsource-4.1.0-32.oe1.aarch64.rpm",
"qemu-4.1.0-32.oe1.aarch64.rpm",
"qemu-img-4.1.0-32.oe1.aarch64.rpm",
"qemu-guest-agent-4.1.0-32.oe1.aarch64.rpm",
"qemu-debuginfo-4.1.0-32.oe1.aarch64.rpm",
"qemu-debugsource-4.1.0-32.oe1.aarch64.rpm",
"qemu-4.1.0-32.oe1.aarch64.rpm",
"qemu-img-4.1.0-32.oe1.aarch64.rpm",
"qemu-guest-agent-4.1.0-32.oe1.aarch64.rpm",
"qemu-debuginfo-4.1.0-32.oe1.aarch64.rpm"
],
"noarch": [
"qemu-help-4.1.0-32.oe1.noarch.rpm",
"qemu-help-4.1.0-32.oe1.noarch.rpm"
],
"src": [
"qemu-4.1.0-32.oe1.src.rpm",
"qemu-4.1.0-32.oe1.src.rpm"
],
"x86_64": [
"qemu-4.1.0-32.oe1.x86_64.rpm",
"qemu-debugsource-4.1.0-32.oe1.x86_64.rpm",
"qemu-img-4.1.0-32.oe1.x86_64.rpm",
"qemu-debuginfo-4.1.0-32.oe1.x86_64.rpm",
"qemu-seabios-4.1.0-32.oe1.x86_64.rpm",
"qemu-guest-agent-4.1.0-32.oe1.x86_64.rpm",
"qemu-4.1.0-32.oe1.x86_64.rpm",
"qemu-debugsource-4.1.0-32.oe1.x86_64.rpm",
"qemu-img-4.1.0-32.oe1.x86_64.rpm",
"qemu-debuginfo-4.1.0-32.oe1.x86_64.rpm",
"qemu-seabios-4.1.0-32.oe1.x86_64.rpm",
"qemu-guest-agent-4.1.0-32.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-32.oe1"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"ecosystem_specific": {
"aarch64": [
"qemu-debugsource-4.1.0-32.oe1.aarch64.rpm",
"qemu-4.1.0-32.oe1.aarch64.rpm",
"qemu-img-4.1.0-32.oe1.aarch64.rpm",
"qemu-guest-agent-4.1.0-32.oe1.aarch64.rpm",
"qemu-debuginfo-4.1.0-32.oe1.aarch64.rpm"
],
"noarch": [
"qemu-help-4.1.0-32.oe1.noarch.rpm"
],
"src": [
"qemu-4.1.0-32.oe1.src.rpm"
],
"x86_64": [
"qemu-4.1.0-32.oe1.x86_64.rpm",
"qemu-debugsource-4.1.0-32.oe1.x86_64.rpm",
"qemu-img-4.1.0-32.oe1.x86_64.rpm",
"qemu-debuginfo-4.1.0-32.oe1.x86_64.rpm",
"qemu-seabios-4.1.0-32.oe1.x86_64.rpm",
"qemu-guest-agent-4.1.0-32.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-32.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\\n\r\nSecurity Fix(es):\\r\\n\\r\\n\r\nA flaw was found in the memory management API of QEMU during the initialization of a memory region cache. This issue could lead to an out-of-bounds write access to the MSI-X table while performing MMIO operations. A guest user may abuse this flaw to crash the QEMU process on the host, resulting in a denial of service. This flaw affects QEMU versions prior to 5.2.0.(CVE-2020-27821)\\r\\n\\r\\n",
"id": "OESA-2021-1012",
"modified": "2026-08-06T11:04:14Z",
"published": "2021-02-04T11:04:14Z",
"references": [
{
"type": "ADVISORY",
"url": "https://openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2021-1012"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2020-27821"
}
],
"schema_version": "1.7.2",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:N/I:N/A:H",
"type": "CVSS_V3"
}
],
"summary": "qemu security update",
"upstream": [
"CVE-2020-27821"
]
}
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.
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.