Skip to content
Fencer Intel
medium 5.5

CVE-2022-1622 json

LibTIFF master branch has an out-of-bounds read in LZWDecode in `libtiff/tif_lzw.c:619`, allowing...

published 4y ago modified 3mo ago also EUVD-2022-24911 , JLSEC-2025-270

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

Summary

LibTIFF master branch has an out-of-bounds read in LZWDecode in libtiff/tif_lzw.c:619, 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 b4e79bfa.

Patch / fix

  • julia Libtiff_jll 4.4.0+0
  • apple iphone_os 16.0
  • apple macos 11.7, 12.6
  • apple tvos 16.0
  • apple watchos 9.0
  • tiff Debian 14, Debian 13, Debian 12 4.4.0~rc1-1

debian advisories DEBIAN-CVE-2022-1622

  • tiff SLES for SAP 15 SP3, SLES for SAP 15 SP2, SLES for SAP 15 SP1 +20 more 4.0.9-150000.45.35.1
  • tiff SLES for SAP 12 SP5, SLES 12 SP5, SLE Software Development Kit 12 SP5 4.0.9-44.74.1

suse advisories SUSE-SU-2023:4869-1SUSE-SU-2023:4736-1

  • libtiff CBL-Mariner 2.0 4.4.0-1

azure linux advisories AZL-9733

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

libtiff: out-of-bounds read in LZWDecode

  • Red Hat Enterprise Linux 6 libtiff Red Hat Enterprise Linux 7 libtiff, libtiff-tools, compat-libtiff3 Red Hat Enterprise Linux 8 libtiff, libtiff-tools, compat-libtiff3 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

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

Exploits and checks

  • gitlab.com https://gitlab.com/libtiff/libtiff/-/issues/410 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
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:N/I:N/A:P
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.3.0+0, <4.4.0+0
4.4.0+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.