# CVE-2022-1210: LibTIFF tiff2ps resource consumption > Attackers can cause a denial of service in LibTIFF's tiff2ps utility by tricking users into opening a malicious TIFF file. - **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L`) - **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 Apr 2022 - **Updated:** 15 Apr 2025 - **Also known as:** AZL-9302, DEBIAN-CVE-2022-1210, ECHO-8e20-aed6-33d5, GHSA-3h6x-gjf3-36gg, JLSEC-2025-268, ROOT-OS-DEBIAN-12-CVE-2022-1210, SUSE-SU-2023:4968-1, SUSE-SU-2023:4969-1, SUSE-SU-2024:2379-1, SUSE-SU-2025:20509-1, SUSE-SU-2025:20663-1, UBUNTU-CVE-2022-1210, openSUSE-SU-2024:13520-1 ## What is CVE-2022-1210? CVE-2022-1210 is a medium-severity denial of service vulnerability in Libtiff Libtiff, published on 3 Apr 2022. 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 A vulnerability classified as problematic was found in LibTIFF 4.3.0. Affected by this vulnerability is the TIFF File Handler of tiff2ps. Opening a malicious file leads to a denial of service. The attack can be launched remotely but requires user interaction. The exploit has been disclosed to the public and may be used. Weakness: CWE-404 (Improper Resource Shutdown or Release), CWE-400 (Uncontrolled Resource Consumption) ## Which versions are affected by CVE-2022-1210? It affects 2 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `jbigkit` | SUSE:Linux Enterprise Micro 5.2 | All versions | 2.1-150000.3.5.1 | | `jbigkit` | SUSE:Linux Enterprise Micro 5.3 | All versions | 2.1-150000.3.5.1 | | `jbigkit` | SUSE:Linux Enterprise Micro 5.4 | All versions | 2.1-150000.3.5.1 | | `jbigkit` | SUSE:Linux Enterprise Micro 5.5 | All versions | 2.1-150000.3.5.1 | | `jbigkit` | SUSE:Linux Enterprise Micro 5.5 | All versions | 2.1-150000.3.5.1 | | `jbigkit` | SUSE:Linux Enterprise Module for Basesystem 15 SP5 | All versions | 2.1-150000.3.5.1 | | `jbigkit` | SUSE:Linux Enterprise Real Time 15 SP4 | All versions | 2.1-150000.3.5.1 | | `jbigkit` | SUSE:Linux Enterprise Server 12 SP5 | All versions | 2.0-14.3.1 | | `jbigkit` | SUSE:Linux Enterprise Server for SAP Applications 12 SP5 | All versions | 2.0-14.3.1 | | `jbigkit` | SUSE:Linux Enterprise Software Development Kit 12 SP5 | All versions | 2.0-14.3.1 | | `jbigkit` | SUSE:Linux Micro 6.0 | All versions | 2.1-4.1 | | `jbigkit` | SUSE:Linux Micro 6.1 | All versions | 2.1-slfo.1.1_2.1 | | `jbigkit` | openSUSE:Leap 15.4 | All versions | 2.1-150000.3.5.1 | | `jbigkit` | openSUSE:Leap 15.5 | All versions | 2.1-150000.3.5.1 | | `jbigkit` | openSUSE:Leap Micro 5.3 | All versions | 2.1-150000.3.5.1 | | `jbigkit` | openSUSE:Leap Micro 5.4 | All versions | 2.1-150000.3.5.1 | | `jbigkit` | openSUSE:Tumbleweed | All versions | 2.1-5.1 | Products: Libtiff Libtiff, Netapp Ontap Select Deploy Administration Utility. ## How do I fix CVE-2022-1210? Apply the vendor's patch. ## Is CVE-2022-1210 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-1210 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-2022-1210 and fix it if it is affected. What it is: CVE-2022-1210 is a medium-severity denial of service vulnerability in Libtiff Libtiff, published on 3 Apr 2022. An attacker can exploit it over the internet without logging in, 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-2022-1210 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-2022-1210/ (Markdown: https://insights.sbomify.com/CVE-2022-1210/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2022-1210 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-1210 - OSV: https://osv.dev/vulnerability/CVE-2022-1210 --- From sbomify Insights: https://insights.sbomify.com/CVE-2022-1210/ Summaries are generated and may contain mistakes; the official description above is the record.