# CVE-2022-3570: Memory corruption in libtiff

> Heap buffer overflows in libtiff allow attackers to cause crashes or disclose information via crafted TIFF files.

- **Severity:** High 7.7 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 Oct 2022
- **Updated:** 7 May 2025
- **Also known as:** ALPINE-CVE-2022-3570, AZL-11283, DEBIAN-CVE-2022-3570, GHSA-w3vw-h42p-vjw6, JLSEC-2025-282, UBUNTU-CVE-2022-3570, openSUSE-SU-2024:12604-1

## What is CVE-2022-3570?

CVE-2022-3570 is a high-severity memory corruption vulnerability in Debian Debian Linux, published on 21 Oct 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Multiple heap buffer overflows in tiffcrop.c utility in libtiff library Version 4.4.0 allows attacker to trigger unsafe or out of bounds memory access via crafted TIFF image file which could result into application crash, potential information disclosure or any other context-dependent impact

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

## Which versions are affected by CVE-2022-3570?

It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `tiff` | openSUSE:Tumbleweed | All versions | 4.5.0-1.1 |

Products: Debian Debian Linux, Libtiff Libtiff.

## How do I fix CVE-2022-3570?

Apply the vendor's patch.

## Is CVE-2022-3570 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-3570 exists.

## Other vulnerabilities in Debian Debian Linux

- [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild)
- [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild)
- [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-3570 and fix it if it is affected.

What it is: CVE-2022-3570 is a high-severity memory corruption vulnerability in Debian Debian Linux, published on 21 Oct 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-3570 exists.

Affected product: Debian Debian Linux. 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-2022-3570/ (Markdown: https://insights.sbomify.com/CVE-2022-3570/index.md)
```

## Sources

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

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