# CVE-2010-0405: Integer overflow in n/a > Integer overflow in bzip2 decompression allows attackers to cause denial of service or execute arbitrary code via crafted compressed files. - **Severity:** Medium 5.1 (`AV:N/AC:H/Au:N/C:P/I:P/A:P`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Not stated - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 28 Sep 2010 - **Updated:** 7 Aug 2024 - **Also known as:** DEBIAN-CVE-2010-0405, DSA-2112-1, GHSA-44gv-7gp8-m9mw, RHSA-2010:0703, RHSA-2010:0858, openSUSE-SU-2024:10132-1 ## What is CVE-2010-0405? CVE-2010-0405 is a medium-severity vulnerability in n/a, published on 28 Sep 2010. ### Official description Integer overflow in the BZ2_decompress function in decompress.c in bzip2 and libbzip2 before 1.0.6 allows context-dependent attackers to cause a denial of service (application crash) or possibly execute arbitrary code via a crafted compressed file. Weakness: CWE-189 ## Which versions are affected by CVE-2010-0405? It affects 2 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `bzip2` | Red Hat:enterprise_linux:3::as | All versions | 0:1.0.2-14.EL3 | | `bzip2-debuginfo` | Red Hat:enterprise_linux:3::as | All versions | 0:1.0.2-14.EL3 | | `bzip2-devel` | Red Hat:enterprise_linux:3::as | All versions | 0:1.0.2-14.EL3 | | `bzip2-libs` | Red Hat:enterprise_linux:3::as | All versions | 0:1.0.2-14.EL3 | | `bzip2` | Red Hat:enterprise_linux:3::desktop | All versions | 0:1.0.2-14.EL3 | | `bzip2-debuginfo` | Red Hat:enterprise_linux:3::desktop | All versions | 0:1.0.2-14.EL3 | | `bzip2-devel` | Red Hat:enterprise_linux:3::desktop | All versions | 0:1.0.2-14.EL3 | | `bzip2-libs` | Red Hat:enterprise_linux:3::desktop | All versions | 0:1.0.2-14.EL3 | | `bzip2` | Red Hat:enterprise_linux:3::es | All versions | 0:1.0.2-14.EL3 | | `bzip2-debuginfo` | Red Hat:enterprise_linux:3::es | All versions | 0:1.0.2-14.EL3 | | `bzip2-devel` | Red Hat:enterprise_linux:3::es | All versions | 0:1.0.2-14.EL3 | | `bzip2-libs` | Red Hat:enterprise_linux:3::es | All versions | 0:1.0.2-14.EL3 | | `bzip2` | Red Hat:enterprise_linux:3::ws | All versions | 0:1.0.2-14.EL3 | | `bzip2-debuginfo` | Red Hat:enterprise_linux:3::ws | All versions | 0:1.0.2-14.EL3 | | `bzip2-devel` | Red Hat:enterprise_linux:3::ws | All versions | 0:1.0.2-14.EL3 | | `bzip2-libs` | Red Hat:enterprise_linux:3::ws | All versions | 0:1.0.2-14.EL3 | | `bzip2` | Red Hat:enterprise_linux:4::as | All versions | 0:1.0.2-16.el4_8 | | `bzip2-debuginfo` | Red Hat:enterprise_linux:4::as | All versions | 0:1.0.2-16.el4_8 | | `bzip2-devel` | Red Hat:enterprise_linux:4::as | All versions | 0:1.0.2-16.el4_8 | | `bzip2-libs` | Red Hat:enterprise_linux:4::as | All versions | 0:1.0.2-16.el4_8 | | `bzip2` | Red Hat:enterprise_linux:4::desktop | All versions | 0:1.0.2-16.el4_8 | | `bzip2-debuginfo` | Red Hat:enterprise_linux:4::desktop | All versions | 0:1.0.2-16.el4_8 | | `bzip2-devel` | Red Hat:enterprise_linux:4::desktop | All versions | 0:1.0.2-16.el4_8 | | `bzip2-libs` | Red Hat:enterprise_linux:4::desktop | All versions | 0:1.0.2-16.el4_8 | | `bzip2` | Red Hat:enterprise_linux:4::es | All versions | 0:1.0.2-16.el4_8 | | `bzip2-debuginfo` | Red Hat:enterprise_linux:4::es | All versions | 0:1.0.2-16.el4_8 | | `bzip2-devel` | Red Hat:enterprise_linux:4::es | All versions | 0:1.0.2-16.el4_8 | | `bzip2-libs` | Red Hat:enterprise_linux:4::es | All versions | 0:1.0.2-16.el4_8 | | `bzip2` | Red Hat:enterprise_linux:4::ws | All versions | 0:1.0.2-16.el4_8 | | `bzip2-debuginfo` | Red Hat:enterprise_linux:4::ws | All versions | 0:1.0.2-16.el4_8 | | `bzip2-devel` | Red Hat:enterprise_linux:4::ws | All versions | 0:1.0.2-16.el4_8 | | `bzip2-libs` | Red Hat:enterprise_linux:4::ws | All versions | 0:1.0.2-16.el4_8 | | `bzip2` | Red Hat:enterprise_linux:5::client | All versions | 0:1.0.3-6.el5_5 | | `bzip2-debuginfo` | Red Hat:enterprise_linux:5::client | All versions | 0:1.0.3-6.el5_5 | | `bzip2-libs` | Red Hat:enterprise_linux:5::client | All versions | 0:1.0.3-6.el5_5 | | `bzip2` | Red Hat:enterprise_linux:5::client_workstation | All versions | 0:1.0.3-6.el5_5 | | `bzip2-debuginfo` | Red Hat:enterprise_linux:5::client_workstation | All versions | 0:1.0.3-6.el5_5 | | `bzip2-devel` | Red Hat:enterprise_linux:5::client_workstation | All versions | 0:1.0.3-6.el5_5 | | `bzip2` | Red Hat:enterprise_linux:5::server | All versions | 0:1.0.3-6.el5_5 | | `bzip2-debuginfo` | Red Hat:enterprise_linux:5::server | All versions | 0:1.0.3-6.el5_5 | Products: Bzip Bzip2, Libzip2 Libzip2. ## How do I fix CVE-2010-0405? Upgrade to a fixed version. ## Is CVE-2010-0405 being exploited? There is no known exploitation of CVE-2010-0405 in the wild and no public exploit code. ## Other vulnerabilities in n/a - [CVE-2019-12900](https://insights.sbomify.com/CVE-2019-12900/): Memory corruption in n/a (critical 9.8) - [CVE-2016-3189](https://insights.sbomify.com/CVE-2016-3189/): Use after free in n/a (medium 6.5) - [CVE-2002-0759](https://insights.sbomify.com/CVE-2002-0759/): Path traversal in n/a (medium 5.0) - [CVE-2011-4089](https://insights.sbomify.com/CVE-2011-4089/): Race condition in n/a (medium 4.6) - [CVE-2008-1372](https://insights.sbomify.com/CVE-2008-1372/): Memory corruption in n/a (medium 4.3) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2010-0405 and fix it if it is affected. What it is: CVE-2010-0405 is a medium-severity vulnerability in n/a, published on 28 Sep 2010. Exploitation: There is no known exploitation of CVE-2010-0405 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-2010-0405/ (Markdown: https://insights.sbomify.com/CVE-2010-0405/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2010-0405 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2010-0405 - OSV: https://osv.dev/vulnerability/CVE-2010-0405 --- From sbomify Insights: https://insights.sbomify.com/CVE-2010-0405/ Summaries are generated and may contain mistakes; the official description above is the record.