First published: Mon Aug 29 2022(Updated: )
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.
Credit: cve@gitlab.com
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/libtiff | <0:4.0.9-26.el8_7 | 0:4.0.9-26.el8_7 |
redhat/libtiff | <0:4.4.0-5.el9_1 | 0:4.4.0-5.el9_1 |
Libtiff Libtiff | <=4.4.0 | |
NetApp ONTAP Select Deploy administration utility | ||
Debian Debian Linux | =11.0 | |
debian/tiff | <=4.1.0+git191117-2~deb10u4<=4.1.0+git191117-2~deb10u8 | 4.2.0-1+deb11u4 4.2.0-1+deb11u5 4.5.0-6+deb12u1 4.5.1+git230720-3 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of CVE-2022-2953 is medium with a severity value of 5.5.
Attackers can exploit CVE-2022-2953 by causing a denial-of-service via a crafted TIFF file.
If you compile libtiff from sources, the fix is available with commit 48d6ece8.
LibTIFF versions 4.2.0-1+deb11u4, 4.5.0-6, and 4.5.1+git230720-1 are affected by CVE-2022-2953.
You can find more information about CVE-2022-2953 on the following references: [GitLab CVE-2022-2953](https://gitlab.com/gitlab-org/cves/-/blob/master/2022/CVE-2022-2953.json), [GitLab Commit 48d6ece8](https://gitlab.com/libtiff/libtiff/-/commit/48d6ece8389b01129e7d357f0985c8f938ce3da3), [GitLab Issue #414](https://gitlab.com/libtiff/libtiff/-/issues/414).