# CVE-2023-52356: Libtiff: segment fault in libtiff in tiffreadrgbatileext() leading to denial of service > A remote attacker can cause a denial of service via heap-buffer overflow in libtiff by providing a crafted TIFF file to the application. - **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:** 25 Jan 2024 - **Updated:** 10 Jun 2026 - **Also known as:** ALSA-2026:7081, AZL-34077, AZL-34955, AZL-43891, AZL-45204, CLSA-2025-1765546516, DEBIAN-CVE-2023-52356, GHSA-cx8g-4cf5-cjv3, MGASA-2024-0055, MINI-hffh-gpmw-pxx8, RHSA-2026:5958, RHSA-2026:7081, RHSA-2026:7304, RLSA-2026:7081, SUSE-SU-2024:0593-1, SUSE-SU-2024:0594-1, UBUNTU-CVE-2023-52356, openSUSE-SU-2024:13627-1 ## What is CVE-2023-52356? CVE-2023-52356 is a high-severity memory corruption vulnerability in Apple Ipados, published on 25 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description A segment fault (SEGV) flaw was found in libtiff that could be triggered by passing a crafted tiff file to the TIFFReadRGBATileExt() API. This flaw allows a remote attacker to cause a heap-buffer overflow, leading to a denial of service. Weakness: CWE-787 (Out-of-bounds Write), CWE-122 (Heap-based Buffer Overflow) ## Which versions are affected by CVE-2023-52356? It affects 14 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `libtiff` | AlmaLinux:10 | All versions | 4.6.0-6.el10_1.2 | | `libtiff-devel` | AlmaLinux:10 | All versions | 4.6.0-6.el10_1.2 | | `libtiff-tools` | AlmaLinux:10 | All versions | 4.6.0-6.el10_1.2 | | `libtiff` | Red Hat:enterprise_linux:10.1 | All versions | 0:4.6.0-6.el10_1.2 | | `libtiff-debuginfo` | Red Hat:enterprise_linux:10.1 | All versions | 0:4.6.0-6.el10_1.2 | | `libtiff-debugsource` | Red Hat:enterprise_linux:10.1 | All versions | 0:4.6.0-6.el10_1.2 | | `libtiff-devel` | Red Hat:enterprise_linux:10.1 | All versions | 0:4.6.0-6.el10_1.2 | | `libtiff-tools` | Red Hat:enterprise_linux:10.1 | All versions | 0:4.6.0-6.el10_1.2 | | `libtiff-tools-debuginfo` | Red Hat:enterprise_linux:10.1 | All versions | 0:4.6.0-6.el10_1.2 | | `libtiff` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:4.6.0-6.el10_0.2 | | `libtiff-tools` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:4.6.0-6.el10_0.2 | | `libtiff` | Red Hat:rhel_eus:9.6::appstream | All versions | 0:4.4.0-13.el9_6.3 | | `libtiff-tools` | Red Hat:rhel_eus:9.6::crb | All versions | 0:4.4.0-13.el9_6.3 | | `libtiff` | Rocky Linux:10 | All versions | 0:4.6.0-6.el10_1.2 | | `tiff` | SUSE:Linux Enterprise Micro 5.2 | All versions | 4.0.9-150000.45.38.1 | | `tiff` | SUSE:Linux Enterprise Micro 5.3 | All versions | 4.0.9-150000.45.38.1 | | `tiff` | SUSE:Linux Enterprise Micro 5.4 | All versions | 4.0.9-150000.45.38.1 | | `tiff` | SUSE:Linux Enterprise Micro 5.5 | All versions | 4.0.9-150000.45.38.1 | | `tiff` | SUSE:Linux Enterprise Module for Basesystem 15 SP5 | All versions | 4.0.9-150000.45.38.1 | | `tiff` | SUSE:Linux Enterprise Module for Package Hub 15 SP5 | All versions | 4.0.9-150000.45.38.1 | | `tiff` | SUSE:Linux Enterprise Server 12 SP5 | All versions | 4.0.9-44.77.1 | | `tiff` | SUSE:Linux Enterprise Server for SAP Applications 12 SP5 | All versions | 4.0.9-44.77.1 | | `tiff` | SUSE:Linux Enterprise Software Development Kit 12 SP5 | All versions | 4.0.9-44.77.1 | | `tiff` | openSUSE:Leap 15.5 | All versions | 4.0.9-150000.45.38.1 | | `tiff` | openSUSE:Leap Micro 5.3 | All versions | 4.0.9-150000.45.38.1 | | `tiff` | openSUSE:Leap Micro 5.4 | All versions | 4.0.9-150000.45.38.1 | | `tiff` | openSUSE:Tumbleweed | All versions | 4.6.0-4.1 | Products: Apple Ipados, Apple Iphone Os, Apple Macos, Apple Tvos, Apple Visionos, Apple Watchos, Debian Debian Linux, Libtiff Libtiff, Redhat Ai Inference Server, Redhat Codeready Linux Builder, Redhat Codeready Linux Builder Eus, Redhat Discovery, Redhat Enterprise Linux, Redhat Enterprise Linux Eus. ## How do I fix CVE-2023-52356? Apply the vendor's patch. ## Is CVE-2023-52356 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-52356 exists. Public exploit code: - Root-cause analysis and patch validation of CVE-2023-52356 in libtiff using AddressSanitizer and GDB. (github_poc): https://github.com/yardenbenita/CVE-2023-52356-libtiff-analysis ## Other vulnerabilities in Apple Ipados - [CVE-2025-43300](https://insights.sbomify.com/CVE-2025-43300/): Apple iOS, iPadOS, and macOS Out-of-Bounds Write (critical 10.0, exploited in the wild) - [CVE-2025-24201](https://insights.sbomify.com/CVE-2025-24201/): Apple Multiple Products WebKit Out-of-Bounds Write (critical 10.0, exploited in the wild) - [CVE-2025-24085](https://insights.sbomify.com/CVE-2025-24085/): Apple Multiple Products Use-After-Free (critical 10.0, exploited in the wild) - [CVE-2025-31200](https://insights.sbomify.com/CVE-2025-31200/): Apple Multiple Products Memory Corruption (critical 9.8, exploited in the wild) - [CVE-2025-31201](https://insights.sbomify.com/CVE-2025-31201/): Apple Multiple Products Arbitrary Read and Write (critical 9.8, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2023-52356 and fix it if it is affected. What it is: CVE-2023-52356 is a high-severity memory corruption vulnerability in Apple Ipados, published on 25 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-52356 exists. Affected product: Apple Ipados. 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-52356/ (Markdown: https://insights.sbomify.com/CVE-2023-52356/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2023-52356 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-52356 - OSV: https://osv.dev/vulnerability/CVE-2023-52356 --- From sbomify Insights: https://insights.sbomify.com/CVE-2023-52356/ Summaries are generated and may contain mistakes; the official description above is the record.