# CVE-2011-0192: Memory corruption in n/a > Remote attackers can execute arbitrary code or cause denial of service via a crafted TIFF file exploiting a buffer overflow in LibTIFF. - **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 3 Mar 2011 - **Updated:** 6 Aug 2024 - **Also known as:** DEBIAN-CVE-2011-0192, GHSA-8jmv-mmc9-gx7j, RHSA-2011:0318 ## What is CVE-2011-0192? CVE-2011-0192 is a critical memory corruption vulnerability in Apple Itunes, published on 3 Mar 2011. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. ### Official description Buffer overflow in Fax4Decode in LibTIFF 3.9.4 and possibly other versions, as used in ImageIO in Apple iTunes before 10.2 on Windows and other products, allows remote attackers to execute arbitrary code or cause a denial of service (application crash) via a crafted TIFF Internet Fax image file that has been compressed using CCITT Group 4 encoding, related to the EXPAND2D macro in libtiff/tif_fax3.h. NOTE: some of these details are obtained from third party information. Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer) ## Which versions are affected by CVE-2011-0192? It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `libtiff` | Red Hat:enterprise_linux:4::as | All versions | 0:3.6.1-17.el4 | | `libtiff-debuginfo` | Red Hat:enterprise_linux:4::as | All versions | 0:3.6.1-17.el4 | | `libtiff-devel` | Red Hat:enterprise_linux:4::as | All versions | 0:3.6.1-17.el4 | | `libtiff` | Red Hat:enterprise_linux:4::desktop | All versions | 0:3.6.1-17.el4 | | `libtiff-debuginfo` | Red Hat:enterprise_linux:4::desktop | All versions | 0:3.6.1-17.el4 | | `libtiff-devel` | Red Hat:enterprise_linux:4::desktop | All versions | 0:3.6.1-17.el4 | | `libtiff` | Red Hat:enterprise_linux:4::es | All versions | 0:3.6.1-17.el4 | | `libtiff-debuginfo` | Red Hat:enterprise_linux:4::es | All versions | 0:3.6.1-17.el4 | | `libtiff-devel` | Red Hat:enterprise_linux:4::es | All versions | 0:3.6.1-17.el4 | | `libtiff` | Red Hat:enterprise_linux:4::ws | All versions | 0:3.6.1-17.el4 | | `libtiff-debuginfo` | Red Hat:enterprise_linux:4::ws | All versions | 0:3.6.1-17.el4 | | `libtiff-devel` | Red Hat:enterprise_linux:4::ws | All versions | 0:3.6.1-17.el4 | | `libtiff` | Red Hat:enterprise_linux:5::server | All versions | 0:3.8.2-7.el5_6.6 | | `libtiff-debuginfo` | Red Hat:enterprise_linux:5::server | All versions | 0:3.8.2-7.el5_6.6 | | `libtiff-devel` | Red Hat:enterprise_linux:5::server | All versions | 0:3.8.2-7.el5_6.6 | | `libtiff` | Red Hat:enterprise_linux:6::client | All versions | 0:3.9.4-1.el6_0.1 | | `libtiff-debuginfo` | Red Hat:enterprise_linux:6::client | All versions | 0:3.9.4-1.el6_0.1 | | `libtiff-devel` | Red Hat:enterprise_linux:6::client | All versions | 0:3.9.4-1.el6_0.1 | | `libtiff-static` | Red Hat:enterprise_linux:6::client | All versions | 0:3.9.4-1.el6_0.1 | | `libtiff` | Red Hat:enterprise_linux:6::computenode | All versions | 0:3.9.4-1.el6_0.1 | | `libtiff-debuginfo` | Red Hat:enterprise_linux:6::computenode | All versions | 0:3.9.4-1.el6_0.1 | | `libtiff-devel` | Red Hat:enterprise_linux:6::computenode | All versions | 0:3.9.4-1.el6_0.1 | | `libtiff-static` | Red Hat:enterprise_linux:6::computenode | All versions | 0:3.9.4-1.el6_0.1 | | `libtiff` | Red Hat:enterprise_linux:6::server | All versions | 0:3.9.4-1.el6_0.1 | | `libtiff-debuginfo` | Red Hat:enterprise_linux:6::server | All versions | 0:3.9.4-1.el6_0.1 | | `libtiff-devel` | Red Hat:enterprise_linux:6::server | All versions | 0:3.9.4-1.el6_0.1 | | `libtiff-static` | Red Hat:enterprise_linux:6::server | All versions | 0:3.9.4-1.el6_0.1 | | `libtiff` | Red Hat:enterprise_linux:6::workstation | All versions | 0:3.9.4-1.el6_0.1 | | `libtiff-debuginfo` | Red Hat:enterprise_linux:6::workstation | All versions | 0:3.9.4-1.el6_0.1 | | `libtiff-devel` | Red Hat:enterprise_linux:6::workstation | All versions | 0:3.9.4-1.el6_0.1 | | `libtiff-static` | Red Hat:enterprise_linux:6::workstation | All versions | 0:3.9.4-1.el6_0.1 | Products: Apple Itunes. ## How do I fix CVE-2011-0192? Upgrade to a fixed version. ## Is CVE-2011-0192 being exploited? There is no known exploitation of CVE-2011-0192 in the wild and no public exploit code. ## Other vulnerabilities in Apple Itunes - [CVE-2010-1763](https://insights.sbomify.com/CVE-2010-1763/): Other in n/a (critical 10.0) - [CVE-2010-1769](https://insights.sbomify.com/CVE-2010-1769/): Memory corruption in n/a (critical 10.0) - [CVE-2013-1035](https://insights.sbomify.com/CVE-2013-1035/): Memory corruption in n/a (critical 9.3) - [CVE-2012-0677](https://insights.sbomify.com/CVE-2012-0677/): Memory corruption in n/a (critical 9.3) - [CVE-2011-3219](https://insights.sbomify.com/CVE-2011-3219/): Memory corruption in n/a (critical 9.3) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2011-0192 and fix it if it is affected. What it is: CVE-2011-0192 is a critical memory corruption vulnerability in Apple Itunes, published on 3 Mar 2011. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2011-0192 in the wild and no public exploit code. Affected product: Apple Itunes. 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-2011-0192/ (Markdown: https://insights.sbomify.com/CVE-2011-0192/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2011-0192 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2011-0192 - OSV: https://osv.dev/vulnerability/CVE-2011-0192 --- From sbomify Insights: https://insights.sbomify.com/CVE-2011-0192/ Summaries are generated and may contain mistakes; the official description above is the record.