# CVE-2020-29443: Memory corruption in n/a > An out-of-bounds read in QEMU's ATAPI command handling allows attackers to disclose memory or cause a denial of service. - **Severity:** Low 3.9 (`CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:L/I:N/A:L`) - **Exploited in the wild:** Not known - **Login needed:** An administrator - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 22 Jan 2021 - **Updated:** 4 Aug 2024 - **Also known as:** DEBIAN-CVE-2020-29443, GHSA-3q92-j8r6-g6h8, RHSA-2021:2322, RHSA-2021:2529, UBUNTU-CVE-2020-29443 ## What is CVE-2020-29443? CVE-2020-29443 is a low-severity memory corruption vulnerability in Debian Debian Linux, published on 22 Jan 2021. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description 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. Weakness: CWE-125 (Out-of-bounds Read) ## Which versions are affected by CVE-2020-29443? It affects 2 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `qemu-img` | Red Hat:enterprise_linux:7::client | All versions | 10:1.5.3-175.el7_9.4 | | `qemu-kvm` | Red Hat:enterprise_linux:7::client | All versions | 10:1.5.3-175.el7_9.4 | | `qemu-kvm-common` | Red Hat:enterprise_linux:7::client | All versions | 10:1.5.3-175.el7_9.4 | | `qemu-kvm-debuginfo` | Red Hat:enterprise_linux:7::client | All versions | 10:1.5.3-175.el7_9.4 | | `qemu-kvm-tools` | Red Hat:enterprise_linux:7::client | All versions | 10:1.5.3-175.el7_9.4 | | `qemu-img` | Red Hat:enterprise_linux:7::computenode | All versions | 10:1.5.3-175.el7_9.4 | | `qemu-kvm` | Red Hat:enterprise_linux:7::computenode | All versions | 10:1.5.3-175.el7_9.4 | | `qemu-kvm-common` | Red Hat:enterprise_linux:7::computenode | All versions | 10:1.5.3-175.el7_9.4 | | `qemu-kvm-debuginfo` | Red Hat:enterprise_linux:7::computenode | All versions | 10:1.5.3-175.el7_9.4 | | `qemu-kvm-tools` | Red Hat:enterprise_linux:7::computenode | All versions | 10:1.5.3-175.el7_9.4 | | `qemu-img-rhev` | Red Hat:enterprise_linux:7::hypervisor | All versions | 10:2.12.0-48.el7_9.3 | | `qemu-kvm-common-rhev` | Red Hat:enterprise_linux:7::hypervisor | All versions | 10:2.12.0-48.el7_9.3 | | `qemu-kvm-rhev` | Red Hat:enterprise_linux:7::hypervisor | All versions | 10:2.12.0-48.el7_9.3 | | `qemu-kvm-rhev-debuginfo` | Red Hat:enterprise_linux:7::hypervisor | All versions | 10:2.12.0-48.el7_9.3 | | `qemu-kvm-tools-rhev` | Red Hat:enterprise_linux:7::hypervisor | All versions | 10:2.12.0-48.el7_9.3 | | `qemu-img` | Red Hat:enterprise_linux:7::server | All versions | 10:1.5.3-175.el7_9.4 | | `qemu-kvm` | Red Hat:enterprise_linux:7::server | All versions | 10:1.5.3-175.el7_9.4 | | `qemu-kvm-common` | Red Hat:enterprise_linux:7::server | All versions | 10:1.5.3-175.el7_9.4 | | `qemu-kvm-debuginfo` | Red Hat:enterprise_linux:7::server | All versions | 10:1.5.3-175.el7_9.4 | | `qemu-kvm-tools` | Red Hat:enterprise_linux:7::server | All versions | 10:1.5.3-175.el7_9.4 | | `qemu-img` | Red Hat:enterprise_linux:7::workstation | All versions | 10:1.5.3-175.el7_9.4 | | `qemu-kvm` | Red Hat:enterprise_linux:7::workstation | All versions | 10:1.5.3-175.el7_9.4 | | `qemu-kvm-common` | Red Hat:enterprise_linux:7::workstation | All versions | 10:1.5.3-175.el7_9.4 | | `qemu-kvm-debuginfo` | Red Hat:enterprise_linux:7::workstation | All versions | 10:1.5.3-175.el7_9.4 | | `qemu-kvm-tools` | Red Hat:enterprise_linux:7::workstation | All versions | 10:1.5.3-175.el7_9.4 | | `qemu-img-rhev` | Red Hat:rhev_manager:4.3 | All versions | 10:2.12.0-48.el7_9.3 | | `qemu-kvm-common-rhev` | Red Hat:rhev_manager:4.3 | All versions | 10:2.12.0-48.el7_9.3 | | `qemu-kvm-rhev` | Red Hat:rhev_manager:4.3 | All versions | 10:2.12.0-48.el7_9.3 | | `qemu-kvm-rhev-debuginfo` | Red Hat:rhev_manager:4.3 | All versions | 10:2.12.0-48.el7_9.3 | | `qemu-kvm-tools-rhev` | Red Hat:rhev_manager:4.3 | All versions | 10:2.12.0-48.el7_9.3 | Products: Debian Debian Linux, Qemu Qemu. ## How do I fix CVE-2020-29443? Apply the vendor's patch. ## Is CVE-2020-29443 being exploited? There is no known exploitation of CVE-2020-29443 in the wild and no public exploit code. ## Other vulnerabilities in Debian Debian Linux - [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild) - [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild) - [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild) - [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild) - [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2020-29443 and fix it if it is affected. What it is: CVE-2020-29443 is a low-severity memory corruption vulnerability in Debian Debian Linux, published on 22 Jan 2021. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2020-29443 in the wild and no public exploit code. Affected product: Debian Debian Linux. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2020-29443/ (Markdown: https://insights.sbomify.com/CVE-2020-29443/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2020-29443 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-29443 - OSV: https://osv.dev/vulnerability/CVE-2020-29443 --- From sbomify Insights: https://insights.sbomify.com/CVE-2020-29443/ Summaries are generated and may contain mistakes; the official description above is the record.