# CVE-2012-0029: Memory corruption in n/a > Guest OS users can trigger a heap buffer overflow in QEMU's e1000 emulation to crash the host or execute arbitrary code. - **Severity:** High 7.4 (`AV:A/AC:M/Au:S/C:C/I:C/A:C`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 27 Jan 2012 - **Updated:** 6 Aug 2024 - **Also known as:** DEBIAN-CVE-2012-0029, DSA-2396-1, DSA-2404-1, GHSA-8rxf-mc82-x3wv, RHSA-2012:0050, RHSA-2012:0370 ## What is CVE-2012-0029? CVE-2012-0029 is a high-severity memory corruption vulnerability in n/a, published on 27 Jan 2012. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description Heap-based buffer overflow in the process_tx_desc function in the e1000 emulation (hw/e1000.c) in qemu-kvm 0.12, and possibly other versions, allows guest OS users to cause a denial of service (QEMU crash) and possibly execute arbitrary code via crafted legacy mode packets. Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer) ## Which versions are affected by CVE-2012-0029? It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `xen` | Red Hat:enterprise_linux:5::client | All versions | 0:3.0.3-135.el5_8.2 | | `xen-debuginfo` | Red Hat:enterprise_linux:5::client | All versions | 0:3.0.3-135.el5_8.2 | | `xen-libs` | Red Hat:enterprise_linux:5::client | All versions | 0:3.0.3-135.el5_8.2 | | `xen` | Red Hat:enterprise_linux:5::server | All versions | 0:3.0.3-135.el5_8.2 | | `xen-debuginfo` | Red Hat:enterprise_linux:5::server | All versions | 0:3.0.3-135.el5_8.2 | | `xen-libs` | Red Hat:enterprise_linux:5::server | All versions | 0:3.0.3-135.el5_8.2 | | `qemu-img` | Red Hat:enterprise_linux:6::client | All versions | 2:0.12.1.2-2.209.el6_2.4 | | `qemu-kvm` | Red Hat:enterprise_linux:6::client | All versions | 2:0.12.1.2-2.209.el6_2.4 | | `qemu-kvm-debuginfo` | Red Hat:enterprise_linux:6::client | All versions | 2:0.12.1.2-2.209.el6_2.4 | | `qemu-kvm-tools` | Red Hat:enterprise_linux:6::client | All versions | 2:0.12.1.2-2.209.el6_2.4 | | `qemu-img` | Red Hat:enterprise_linux:6::computenode | All versions | 2:0.12.1.2-2.209.el6_2.4 | | `qemu-kvm` | Red Hat:enterprise_linux:6::computenode | All versions | 2:0.12.1.2-2.209.el6_2.4 | | `qemu-kvm-debuginfo` | Red Hat:enterprise_linux:6::computenode | All versions | 2:0.12.1.2-2.209.el6_2.4 | | `qemu-kvm-tools` | Red Hat:enterprise_linux:6::computenode | All versions | 2:0.12.1.2-2.209.el6_2.4 | | `qemu-img` | Red Hat:enterprise_linux:6::server | All versions | 2:0.12.1.2-2.209.el6_2.4 | | `qemu-kvm` | Red Hat:enterprise_linux:6::server | All versions | 2:0.12.1.2-2.209.el6_2.4 | | `qemu-kvm-debuginfo` | Red Hat:enterprise_linux:6::server | All versions | 2:0.12.1.2-2.209.el6_2.4 | | `qemu-kvm-tools` | Red Hat:enterprise_linux:6::server | All versions | 2:0.12.1.2-2.209.el6_2.4 | | `qemu-img` | Red Hat:enterprise_linux:6::workstation | All versions | 2:0.12.1.2-2.209.el6_2.4 | | `qemu-kvm` | Red Hat:enterprise_linux:6::workstation | All versions | 2:0.12.1.2-2.209.el6_2.4 | | `qemu-kvm-debuginfo` | Red Hat:enterprise_linux:6::workstation | All versions | 2:0.12.1.2-2.209.el6_2.4 | | `qemu-kvm-tools` | Red Hat:enterprise_linux:6::workstation | All versions | 2:0.12.1.2-2.209.el6_2.4 | | `xen` | Red Hat:rhel_virtualization:5::client | All versions | 0:3.0.3-135.el5_8.2 | | `xen-debuginfo` | Red Hat:rhel_virtualization:5::client | All versions | 0:3.0.3-135.el5_8.2 | | `xen-devel` | Red Hat:rhel_virtualization:5::client | All versions | 0:3.0.3-135.el5_8.2 | | `xen` | Red Hat:rhel_virtualization:5::server | All versions | 0:3.0.3-135.el5_8.2 | | `xen-debuginfo` | Red Hat:rhel_virtualization:5::server | All versions | 0:3.0.3-135.el5_8.2 | | `xen-devel` | Red Hat:rhel_virtualization:5::server | All versions | 0:3.0.3-135.el5_8.2 | Products: Kvm Group Qemu-Kvm. ## How do I fix CVE-2012-0029? Apply the vendor's patch. ## Is CVE-2012-0029 being exploited? There is no known exploitation of CVE-2012-0029 in the wild and no public exploit code. ## Other vulnerabilities in n/a - [CVE-2011-2512](https://insights.sbomify.com/CVE-2011-2512/): Integer overflow in n/a (medium 5.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2012-0029 and fix it if it is affected. What it is: CVE-2012-0029 is a high-severity memory corruption vulnerability in n/a, published on 27 Jan 2012. 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-2012-0029 in the wild and no public exploit code. Affected product: n/a. 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-2012-0029/ (Markdown: https://insights.sbomify.com/CVE-2012-0029/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2012-0029 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2012-0029 - OSV: https://osv.dev/vulnerability/CVE-2012-0029 --- From sbomify Insights: https://insights.sbomify.com/CVE-2012-0029/ Summaries are generated and may contain mistakes; the official description above is the record.