# CVE-2019-12900: Memory corruption in n/a > An out-of-bounds write in bzip2 decompression allows attackers to execute arbitrary code or cause denial of service via crafted files. - **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 19 Jun 2019 - **Updated:** 14 Oct 2026 - **Also known as:** ALPINE-CVE-2019-12900, ALSA-2024:8922, ALSA-2025:0733, ALSA-2025:0925, CLEANSTART-2026-PN21117, CLSA-2024-1731337736, CLSA-2024-1731340993, CLSA-2024-1731341386, CLSA-2026-1777969769, CLSA-2026-1778047964, DEBIAN-CVE-2019-12900, GHSA-j686-6fc2-2525, HSEC-2024-0002, JLSEC-2025-11, MGASA-2019-0338, PSF-2019-4, RHSA-2024:10803, RHSA-2024:8922, RHSA-2025:0733, RHSA-2025:0925, RLSA-2024:8922, RLSA-2025:0733, RLSA-2025:0925, SUSE-SU-2019:14139-1, SUSE-SU-2019:1846-1, SUSE-SU-2019:2004-1, SUSE-SU-2019:2013-1, SUSE-SU-2019:2013-2, UBUNTU-CVE-2019-12900, openSUSE-SU-2019:1781-1, openSUSE-SU-2019:1918-1 ## What is CVE-2019-12900? CVE-2019-12900 is a critical memory corruption vulnerability in Canonical Ubuntu Linux, published on 19 Jun 2019. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description BZ2_decompress in decompress.c in bzip2 through 1.0.6 has an out-of-bounds write when there are many selectors. Weakness: CWE-787 (Out-of-bounds Write) ## Which versions are affected by CVE-2019-12900? 3 open source packages ship an affected version, including bz2, bzlib and bzlib-conduit. It affects 6 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `bz2` | Hackage | From 0.1.0.0 | 1.0.1.1 | | `bzlib` | Hackage | From 0.4 | 0.5.2.0 | | `bzlib-conduit` | Hackage | From 0.1.0.0 | 0.3.0.3 | | `bzip2` | AlmaLinux:8 | All versions | 1.0.6-27.el8_10 | | `bzip2` | AlmaLinux:8 | All versions | 1.0.6-28.el8_10 | | `bzip2-devel` | AlmaLinux:8 | All versions | 1.0.6-27.el8_10 | | `bzip2-devel` | AlmaLinux:8 | All versions | 1.0.6-28.el8_10 | | `bzip2-libs` | AlmaLinux:8 | All versions | 1.0.6-27.el8_10 | | `bzip2-libs` | AlmaLinux:8 | All versions | 1.0.6-28.el8_10 | | `bzip2` | AlmaLinux:9 | All versions | 1.0.8-10.el9_5 | | `bzip2-devel` | AlmaLinux:9 | All versions | 1.0.8-10.el9_5 | | `bzip2-libs` | AlmaLinux:9 | All versions | 1.0.8-10.el9_5 | | `bzip2` | Red Hat:enterprise_linux:8::baseos | All versions | 0:1.0.6-27.el8_10 | | `bzip2` | Red Hat:enterprise_linux:8::baseos | All versions | 0:1.0.6-28.el8_10 | | `bzip2-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:1.0.6-27.el8_10 | | `bzip2-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:1.0.6-28.el8_10 | | `bzip2-debugsource` | Red Hat:enterprise_linux:8::baseos | All versions | 0:1.0.6-27.el8_10 | | `bzip2-debugsource` | Red Hat:enterprise_linux:8::baseos | All versions | 0:1.0.6-28.el8_10 | | `bzip2-devel` | Red Hat:enterprise_linux:8::baseos | All versions | 0:1.0.6-27.el8_10 | | `bzip2-devel` | Red Hat:enterprise_linux:8::baseos | All versions | 0:1.0.6-28.el8_10 | | `bzip2-libs` | Red Hat:enterprise_linux:8::baseos | All versions | 0:1.0.6-27.el8_10 | | `bzip2-libs` | Red Hat:enterprise_linux:8::baseos | All versions | 0:1.0.6-28.el8_10 | | `bzip2-libs-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:1.0.6-27.el8_10 | | `bzip2-libs-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:1.0.6-28.el8_10 | | `bzip2-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:1.0.8-10.el9_5 | | `bzip2-debugsource` | Red Hat:enterprise_linux:9::appstream | All versions | 0:1.0.8-10.el9_5 | | `bzip2-devel` | Red Hat:enterprise_linux:9::appstream | All versions | 0:1.0.8-10.el9_5 | | `bzip2-libs-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:1.0.8-10.el9_5 | | `bzip2` | Red Hat:enterprise_linux:9::baseos | All versions | 0:1.0.8-10.el9_5 | | `bzip2-debuginfo` | Red Hat:enterprise_linux:9::baseos | All versions | 0:1.0.8-10.el9_5 | | `bzip2-debugsource` | Red Hat:enterprise_linux:9::baseos | All versions | 0:1.0.8-10.el9_5 | | `bzip2-libs` | Red Hat:enterprise_linux:9::baseos | All versions | 0:1.0.8-10.el9_5 | | `bzip2-libs-debuginfo` | Red Hat:enterprise_linux:9::baseos | All versions | 0:1.0.8-10.el9_5 | | `bzip2-debuginfo` | Red Hat:rhel_eus:9.4::appstream | All versions | 0:1.0.8-8.el9_4.1 | | `bzip2-debugsource` | Red Hat:rhel_eus:9.4::appstream | All versions | 0:1.0.8-8.el9_4.1 | | `bzip2-devel` | Red Hat:rhel_eus:9.4::appstream | All versions | 0:1.0.8-8.el9_4.1 | | `bzip2-libs-debuginfo` | Red Hat:rhel_eus:9.4::appstream | All versions | 0:1.0.8-8.el9_4.1 | | `bzip2` | Red Hat:rhel_eus:9.4::baseos | All versions | 0:1.0.8-8.el9_4.1 | | `bzip2-debuginfo` | Red Hat:rhel_eus:9.4::baseos | All versions | 0:1.0.8-8.el9_4.1 | | `bzip2-debugsource` | Red Hat:rhel_eus:9.4::baseos | All versions | 0:1.0.8-8.el9_4.1 | Products: Bzip Bzip2, Canonical Ubuntu Linux, Debian Debian Linux, Freebsd Freebsd, Opensuse Leap, Python Python. ## How do I fix CVE-2019-12900? Upgrade bz2 to 1.0.1.1 or later. ## Is CVE-2019-12900 being exploited? There is no known exploitation of CVE-2019-12900 in the wild and no public exploit code. ## Other vulnerabilities in Canonical Ubuntu Linux - [CVE-2016-3189](https://insights.sbomify.com/CVE-2016-3189/): Use after free in n/a (medium 6.5) - [CVE-2010-0405](https://insights.sbomify.com/CVE-2010-0405/): Integer overflow in n/a (medium 5.1) - [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-2019-12900 and fix it if it is affected. What it is: CVE-2019-12900 is a critical memory corruption vulnerability in Canonical Ubuntu Linux, published on 19 Jun 2019. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2019-12900 in the wild and no public exploit code. Affected packages and fixed versions: - bz2 (Hackage): affected from 0.1.0.0; fixed in 1.0.1.1 - bzlib (Hackage): affected from 0.4; fixed in 0.5.2.0 - bzlib-conduit (Hackage): affected from 0.1.0.0; fixed in 0.3.0.3 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-2019-12900/ (Markdown: https://insights.sbomify.com/CVE-2019-12900/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2019-12900 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-12900 - OSV: https://osv.dev/vulnerability/CVE-2019-12900 --- From sbomify Insights: https://insights.sbomify.com/CVE-2019-12900/ Summaries are generated and may contain mistakes; the official description above is the record.