Skip to content
Fencer Intel
medium 5.5

CVE-2022-2953 json

LibTIFF 4.4.0 has an out-of-bounds read in extractImageSection in `tools/tiffcrop.c:6905`, allowing...

published 4y ago modified 3mo ago also EUVD-2022-35174 , JLSEC-2025-279

cvss
5.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.6%
EPSS 0.6% chance of exploitation in 30 days, percentile 47%
public exploits
0
none known

Summary

LibTIFF 4.4.0 has an out-of-bounds read in extractImageSection in tools/tiffcrop.c:6905, allowing attackers to cause a denial-of-service via a crafted tiff file. For users that compile libtiff from sources, the fix is available with commit 48d6ece8.

Patch / fix

  • julia Libtiff_jll 4.5.1+0
  • tiff Debian 14, Debian 13, Debian 12 4.4.0-6

debian advisories DEBIAN-CVE-2022-2953

  • libtiff RHEL 8 4.0.9-26.el8_7
  • libtiff-tools RHEL 8 4.0.9-26.el8_7
  • libtiff RHEL 9 4.4.0-5.el9_1
  • libtiff-tools RHEL 9 4.4.0-5.el9_1

red hat advisories RHSA-2023:0095RHSA-2023:0302

  • libtiff AlmaLinux 9 4.4.0-5.el9_1
  • libtiff-tools AlmaLinux 9 4.4.0-5.el9_1
  • libtiff AlmaLinux 8 4.0.9-26.el8_7
  • libtiff-tools AlmaLinux 8 4.0.9-26.el8_7

almalinux advisories ALSA-2023:0302ALSA-2023:0095

  • libtiff Rocky Linux 9 4.4.0-5.el9_1
  • libtiff Rocky Linux 8 4.0.9-26.el8_7

rocky linux advisories RLSA-2023:0302RLSA-2023:0095

  • tiff Alpine 3.17 4.4.0-r1
  • tiff Alpine 3.24, Alpine 3.23, Alpine 3.22 +4 more 4.5.0-r0

alpine advisories ALPINE-CVE-2022-2953

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • libtiff CBL-Mariner 2.0 4.4.0-4

azure linux advisories AZL-10762

Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT

Is CVE-2022-2953 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2022-2953 updated cvss 5.5

libtiff: tiffcrop: heap-buffer-overflow in extractImageSection in tiffcrop.c

  • Red Hat Enterprise Linux 6 libtiff Red Hat Enterprise Linux 7 libtiff, libtiff-tools, compat-libtiff3
    affected: no fix planned “Out of support scope”
  • Red Hat Enterprise Linux 8 compat-libtiff3
    affected: no fix planned “Will not fix”
  • Red Hat CodeReady Linux Builder (v. 8) libtiff-tools 4.0.9-26.el8_7
    fixed: vendor fix RHSA-2023:0095
  • Red Hat CodeReady Linux Builder (v. 9) libtiff-tools 4.4.0-5.el9_1
    fixed: vendor fix RHSA-2023:0302
  • Red Hat Enterprise Linux AppStream (v. 8) libtiff 4.0.9-26.el8_7
    fixed: vendor fix RHSA-2023:0095
  • Red Hat Enterprise Linux AppStream (v. 9) libtiff 4.4.0-5.el9_1
    fixed: vendor fix RHSA-2023:0302

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.58% chance of exploitation in the next 30 days, higher than 47% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • gitlab.com https://gitlab.com/libtiff/libtiff/-/issues/414 referenced PoC, tagged "exploit" by a source, unverified
  • gitlab.com https://gitlab.com/gitlab-org/cves/-/blob/master/2022/CVE-2022-2953.json referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
NVD 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
OSV 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

Affected packages

ecosystem package affected fixed in
julia Libtiff_jll
<4.5.1+0
4.5.1+0

Affected products

  • libtiff libtiff

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.