Skip to content
Fencer Intel
medium 5.5

CVE-2022-2867 json

libtiff's tiffcrop utility has a `uint32_t` underflow that can lead to out of bounds read and write....

published 4y ago modified 3mo ago also EUVD-2022-35101 , JLSEC-2025-276

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

Summary

libtiff's tiffcrop utility has a uint32_t underflow that can lead to out of bounds read and write. An attacker who supplies a crafted file to tiffcrop (likely via tricking a user to run tiffcrop on it with certain parameters) could cause a crash or in some cases, further exploitation.

Patch / fix

  • julia Libtiff_jll 4.4.0+0
  • libtiff libtiff 4.4.0
  • tiff Debian 14, Debian 13, Debian 12 4.4.0~rc1-1

debian advisories DEBIAN-CVE-2022-2867

  • tiff Ubuntu 18.04 LTS 4.0.9-5ubuntu0.8
  • tiff Ubuntu 20.04 LTS 4.1.0+git191117-2ubuntu0.20.04.6
  • tiff Ubuntu 22.04 LTS 4.3.0-6ubuntu0.2
  • tiff Ubuntu Pro 14.04 LTS 4.0.3-7ubuntu0.11+esm3
  • tiff Ubuntu Pro 16.04 LTS 4.0.6-1ubuntu0.8+esm3

ubuntu advisories UBUNTU-CVE-2022-2867

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • libtiff RHEL 8 4.0.9-26.el8_7
  • libtiff-tools RHEL 8 4.0.9-26.el8_7

red hat advisories RHSA-2023:0095

  • tiff SLES for SAP 15 SP2, SLES for SAP 15 SP1, SLES for SAP 15 +26 more 4.0.9-150000.45.16.1
  • tiff SLES for SAP 12 SP5, SLES for SAP 12 SP4, SLES 12 SP5 +6 more 4.0.9-44.56.1

suse advisories SUSE-SU-2022:3690-1SUSE-SU-2022:3679-1

  • tiff openSUSE Tumbleweed 4.6.0-2.1

opensuse advisories openSUSE-SU-2024:13381-1

  • libtiff AlmaLinux 8 4.0.9-26.el8_7
  • libtiff-tools AlmaLinux 8 4.0.9-26.el8_7

almalinux advisories ALSA-2023:0095

  • libtiff Rocky Linux 8 4.0.9-26.el8_7

rocky linux advisories RLSA-2023:0095

  • tiff Alpine 3.24, Alpine 3.23, Alpine 3.22 +9 more 4.4.0-r0

alpine advisories ALPINE-CVE-2022-2867

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.5.0-1

azure linux advisories AZL-10567

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-2867 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-2867 updated cvss 5.5

libtiff: uint32_t underflow leads to out of bounds read and write 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 Red Hat Enterprise Linux AppStream (v. 8) libtiff 4.0.9-26.el8_7
    fixed: vendor fix RHSA-2023:0095
  • Red Hat Enterprise Linux 9 libtiff, libtiff-tools
    not affected: vulnerable code not present

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.32% chance of exploitation in the next 30 days, higher than 25% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
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.4.0+0
4.4.0+0

Affected products

  • n/a 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.