# CVE-2023-52355: Libtiff: tiffrasterscanlinesize64 produce too-big size and could cause oom

> A remote attacker can cause a denial of service via out-of-memory conditions by providing a crafted TIFF file to the libtiff 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:** 25 Jan 2024
- **Updated:** 2 Oct 2026
- **Also known as:** DEBIAN-CVE-2023-52355, ECHO-cc40-27fe-5c1c, GHSA-fh6j-mgh8-7prh, JLSEC-2025-315, RHSA-2026:43537, ROOT-OS-DEBIAN-11-CVE-2023-52355, ROOT-OS-DEBIAN-12-CVE-2023-52355, UBUNTU-CVE-2023-52355

## What is CVE-2023-52355?

CVE-2023-52355 is a high-severity denial of service vulnerability in Libtiff Libtiff, published on 25 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An out-of-memory flaw was found in libtiff that could be triggered by passing a crafted tiff file to the TIFFRasterScanlineSize64() API. This flaw allows a remote attacker to cause a denial of service via a crafted input with a size smaller than 379 KB.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2023-52355?

It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libtiff` | Red Hat:rhel_eus:9.6::appstream | All versions | 0:4.4.0-13.el9_6.5 |
| `libtiff-debuginfo` | Red Hat:rhel_eus:9.6::appstream | All versions | 0:4.4.0-13.el9_6.5 |
| `libtiff-debugsource` | Red Hat:rhel_eus:9.6::appstream | All versions | 0:4.4.0-13.el9_6.5 |
| `libtiff-devel` | Red Hat:rhel_eus:9.6::appstream | All versions | 0:4.4.0-13.el9_6.5 |
| `libtiff-tools-debuginfo` | Red Hat:rhel_eus:9.6::appstream | All versions | 0:4.4.0-13.el9_6.5 |
| `libtiff-debuginfo` | Red Hat:rhel_eus:9.6::crb | All versions | 0:4.4.0-13.el9_6.5 |
| `libtiff-debugsource` | Red Hat:rhel_eus:9.6::crb | All versions | 0:4.4.0-13.el9_6.5 |
| `libtiff-tools` | Red Hat:rhel_eus:9.6::crb | All versions | 0:4.4.0-13.el9_6.5 |
| `libtiff-tools-debuginfo` | Red Hat:rhel_eus:9.6::crb | All versions | 0:4.4.0-13.el9_6.5 |

Products: Libtiff Libtiff, Redhat Enterprise Linux.

## How do I fix CVE-2023-52355?

Apply the vendor's patch.

## Is CVE-2023-52355 being exploited?

There is no known exploitation of CVE-2023-52355 in the wild and no public exploit code.

## 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-52355 and fix it if it is affected.

What it is: CVE-2023-52355 is a high-severity denial of service vulnerability in Libtiff Libtiff, published on 25 Jan 2024. 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-2023-52355 in the wild and no public exploit code.

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-52355/ (Markdown: https://insights.sbomify.com/CVE-2023-52355/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-52355
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-52355
- OSV: https://osv.dev/vulnerability/CVE-2023-52355

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-52355/
Summaries are generated and may contain mistakes; the official description above is the record.