# CVE-2005-0891: Memory corruption in n/a > Remote attackers can cause a denial of service via a crafted BMP image due to a double free vulnerability in the GTK2 library. - **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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:** 1 Apr 2005 - **Updated:** 7 Aug 2024 - **Also known as:** DEBIAN-CVE-2005-0891, GHSA-f6r7-g7pj-vhjx, RHSA-2005:343, RHSA-2005:344 ## What is CVE-2005-0891? CVE-2005-0891 is a high-severity memory corruption vulnerability in n/a, published on 1 Apr 2005. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description Double free vulnerability in gtk 2 (gtk2) before 2.2.4 allows remote attackers to cause a denial of service (crash) via a crafted BMP image. Weakness: CWE-415 (Double Free) ## Which versions are affected by CVE-2005-0891? It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `gdk-pixbuf` | Red Hat:enterprise_linux:3::as | All versions | 1:0.22.0-12.el3 | | `gdk-pixbuf-debuginfo` | Red Hat:enterprise_linux:3::as | All versions | 1:0.22.0-12.el3 | | `gdk-pixbuf-devel` | Red Hat:enterprise_linux:3::as | All versions | 1:0.22.0-12.el3 | | `gdk-pixbuf-gnome` | Red Hat:enterprise_linux:3::as | All versions | 1:0.22.0-12.el3 | | `gtk2` | Red Hat:enterprise_linux:3::as | All versions | 0:2.2.4-15 | | `gtk2-debuginfo` | Red Hat:enterprise_linux:3::as | All versions | 0:2.2.4-15 | | `gtk2-devel` | Red Hat:enterprise_linux:3::as | All versions | 0:2.2.4-15 | | `gdk-pixbuf` | Red Hat:enterprise_linux:3::desktop | All versions | 1:0.22.0-12.el3 | | `gdk-pixbuf-debuginfo` | Red Hat:enterprise_linux:3::desktop | All versions | 1:0.22.0-12.el3 | | `gdk-pixbuf-devel` | Red Hat:enterprise_linux:3::desktop | All versions | 1:0.22.0-12.el3 | | `gdk-pixbuf-gnome` | Red Hat:enterprise_linux:3::desktop | All versions | 1:0.22.0-12.el3 | | `gtk2` | Red Hat:enterprise_linux:3::desktop | All versions | 0:2.2.4-15 | | `gtk2-debuginfo` | Red Hat:enterprise_linux:3::desktop | All versions | 0:2.2.4-15 | | `gtk2-devel` | Red Hat:enterprise_linux:3::desktop | All versions | 0:2.2.4-15 | | `gdk-pixbuf` | Red Hat:enterprise_linux:3::es | All versions | 1:0.22.0-12.el3 | | `gdk-pixbuf-debuginfo` | Red Hat:enterprise_linux:3::es | All versions | 1:0.22.0-12.el3 | | `gdk-pixbuf-devel` | Red Hat:enterprise_linux:3::es | All versions | 1:0.22.0-12.el3 | | `gdk-pixbuf-gnome` | Red Hat:enterprise_linux:3::es | All versions | 1:0.22.0-12.el3 | | `gtk2` | Red Hat:enterprise_linux:3::es | All versions | 0:2.2.4-15 | | `gtk2-debuginfo` | Red Hat:enterprise_linux:3::es | All versions | 0:2.2.4-15 | | `gtk2-devel` | Red Hat:enterprise_linux:3::es | All versions | 0:2.2.4-15 | | `gdk-pixbuf` | Red Hat:enterprise_linux:3::ws | All versions | 1:0.22.0-12.el3 | | `gdk-pixbuf-debuginfo` | Red Hat:enterprise_linux:3::ws | All versions | 1:0.22.0-12.el3 | | `gdk-pixbuf-devel` | Red Hat:enterprise_linux:3::ws | All versions | 1:0.22.0-12.el3 | | `gdk-pixbuf-gnome` | Red Hat:enterprise_linux:3::ws | All versions | 1:0.22.0-12.el3 | | `gtk2` | Red Hat:enterprise_linux:3::ws | All versions | 0:2.2.4-15 | | `gtk2-debuginfo` | Red Hat:enterprise_linux:3::ws | All versions | 0:2.2.4-15 | | `gtk2-devel` | Red Hat:enterprise_linux:3::ws | All versions | 0:2.2.4-15 | | `gdk-pixbuf` | Red Hat:enterprise_linux:4::as | All versions | 1:0.22.0-16.el4 | | `gdk-pixbuf-debuginfo` | Red Hat:enterprise_linux:4::as | All versions | 1:0.22.0-16.el4 | | `gdk-pixbuf-devel` | Red Hat:enterprise_linux:4::as | All versions | 1:0.22.0-16.el4 | | `gtk2` | Red Hat:enterprise_linux:4::as | All versions | 0:2.4.13-14 | | `gtk2-debuginfo` | Red Hat:enterprise_linux:4::as | All versions | 0:2.4.13-14 | | `gtk2-devel` | Red Hat:enterprise_linux:4::as | All versions | 0:2.4.13-14 | | `gdk-pixbuf` | Red Hat:enterprise_linux:4::desktop | All versions | 1:0.22.0-16.el4 | | `gdk-pixbuf-debuginfo` | Red Hat:enterprise_linux:4::desktop | All versions | 1:0.22.0-16.el4 | | `gdk-pixbuf-devel` | Red Hat:enterprise_linux:4::desktop | All versions | 1:0.22.0-16.el4 | | `gtk2` | Red Hat:enterprise_linux:4::desktop | All versions | 0:2.4.13-14 | | `gtk2-debuginfo` | Red Hat:enterprise_linux:4::desktop | All versions | 0:2.4.13-14 | | `gtk2-devel` | Red Hat:enterprise_linux:4::desktop | All versions | 0:2.4.13-14 | Products: Gnome Gtk. ## How do I fix CVE-2005-0891? Upgrade to a fixed version. ## Is CVE-2005-0891 being exploited? There is no known exploitation of CVE-2005-0891 in the wild and no public exploit code. ## Other vulnerabilities in n/a - [CVE-2012-0828](https://insights.sbomify.com/CVE-2012-0828/): Memory corruption in Xchat-WDK (critical 9.8) - [CVE-2010-4833](https://insights.sbomify.com/CVE-2010-4833/): Path traversal in n/a (critical 9.3) - [CVE-2001-0084](https://insights.sbomify.com/CVE-2001-0084/): Privilege escalation in n/a (high 7.2) - [CVE-2010-4831](https://insights.sbomify.com/CVE-2010-4831/): Path traversal in n/a (medium 6.9) - [CVE-2010-0732](https://insights.sbomify.com/CVE-2010-0732/): Race condition in n/a (medium 6.2) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2005-0891 and fix it if it is affected. What it is: CVE-2005-0891 is a high-severity memory corruption vulnerability in n/a, published on 1 Apr 2005. 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-2005-0891 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-2005-0891/ (Markdown: https://insights.sbomify.com/CVE-2005-0891/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2005-0891 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2005-0891 - OSV: https://osv.dev/vulnerability/CVE-2005-0891 --- From sbomify Insights: https://insights.sbomify.com/CVE-2005-0891/ Summaries are generated and may contain mistakes; the official description above is the record.