# CVE-2023-3164: Heap-buffer-overflow in extractimagesection() > Attackers can cause a denial of service in applications using LibTIFF by providing a crafted TIFF file that triggers a heap-buffer-overflow. - **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Local or same network only - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 2 Nov 2023 - **Updated:** 11 Oct 2024 - **Also known as:** AZL-31765, AZL-34952, DEBIAN-CVE-2023-3164, ECHO-cc50-4ed5-0244, GHSA-2x8c-h7r9-r6m6, JLSEC-2025-314, MGASA-2024-0213, ROOT-OS-DEBIAN-12-CVE-2023-3164, SUSE-SU-2024:1892-1, SUSE-SU-2024:2028-1, SUSE-SU-2024:2028-2, UBUNTU-CVE-2023-3164, USN-6827-1 ## What is CVE-2023-3164? CVE-2023-3164 is a medium-severity memory corruption vulnerability in Libtiff Libtiff, published on 2 Nov 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link. ### Official description A heap-buffer-overflow vulnerability was found in LibTIFF, in extractImageSection() at tools/tiffcrop.c:7916 and tools/tiffcrop.c:7801. This flaw allows attackers to cause a denial of service via a crafted tiff file. Weakness: CWE-787 (Out-of-bounds Write), CWE-120 (Buffer Copy without Checking Size of Input) ## Which versions are affected by CVE-2023-3164? It affects 2 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `tiff` | SUSE:Linux Enterprise Micro 5.2 | All versions | 4.0.9-150000.45.44.1 | | `tiff` | SUSE:Linux Enterprise Micro 5.3 | All versions | 4.0.9-150000.45.44.1 | | `tiff` | SUSE:Linux Enterprise Micro 5.4 | All versions | 4.0.9-150000.45.44.1 | | `tiff` | SUSE:Linux Enterprise Micro 5.5 | All versions | 4.0.9-150000.45.44.1 | | `tiff` | SUSE:Linux Enterprise Micro 5.5 | All versions | 4.0.9-150000.45.44.1 | | `tiff` | SUSE:Linux Enterprise Module for Basesystem 15 SP5 | All versions | 4.0.9-150000.45.44.1 | | `tiff` | SUSE:Linux Enterprise Module for Basesystem 15 SP6 | All versions | 4.0.9-150000.45.44.1 | | `tiff` | SUSE:Linux Enterprise Module for Package Hub 15 SP5 | All versions | 4.0.9-150000.45.44.1 | | `tiff` | SUSE:Linux Enterprise Server 12 SP5 | All versions | 4.0.9-44.83.1 | | `tiff` | SUSE:Linux Enterprise Server for SAP Applications 12 SP5 | All versions | 4.0.9-44.83.1 | | `tiff` | SUSE:Linux Enterprise Software Development Kit 12 SP5 | All versions | 4.0.9-44.83.1 | | `tiff` | openSUSE:Leap 15.5 | All versions | 4.0.9-150000.45.44.1 | | `tiff` | openSUSE:Leap Micro 5.3 | All versions | 4.0.9-150000.45.44.1 | | `tiff` | openSUSE:Leap Micro 5.4 | All versions | 4.0.9-150000.45.44.1 | Products: Libtiff Libtiff, Redhat Enterprise Linux. ## How do I fix CVE-2023-3164? Apply the vendor's patch. ## Is CVE-2023-3164 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-3164 exists. ## Other vulnerabilities in Libtiff Libtiff - [CVE-2004-1308](https://insights.sbomify.com/CVE-2004-1308/): Integer overflow in n/a (critical 10.0) - [CVE-2004-0929](https://insights.sbomify.com/CVE-2004-0929/): Memory corruption in n/a (critical 10.0) - [CVE-2025-61144](https://insights.sbomify.com/CVE-2025-61144/): Memory corruption in n/a (critical 9.8) - [CVE-2016-9533](https://insights.sbomify.com/CVE-2016-9533/): Memory corruption in n/a (critical 9.8) - [CVE-2016-9534](https://insights.sbomify.com/CVE-2016-9534/): Memory corruption in n/a (critical 9.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2023-3164 and fix it if it is affected. What it is: CVE-2023-3164 is a medium-severity memory corruption vulnerability in Libtiff Libtiff, published on 2 Nov 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-3164 exists. Affected product: Libtiff Libtiff. 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-2023-3164/ (Markdown: https://insights.sbomify.com/CVE-2023-3164/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2023-3164 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-3164 - OSV: https://osv.dev/vulnerability/CVE-2023-3164 --- From sbomify Insights: https://insights.sbomify.com/CVE-2023-3164/ Summaries are generated and may contain mistakes; the official description above is the record.