LibTIFF 4.4.0 has an out-of-bounds write in _TIFFmemcpy in libtiff/tif_unix.c:346 when called from extractImageSection, tools/tiffcrop.c:6860, 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 236b7191.
References
Configurations
History
21 Nov 2024, 07:19
Type | Values Removed | Values Added |
---|---|---|
References | () https://gitlab.com/gitlab-org/cves/-/blob/master/2022/CVE-2022-3627.json - Third Party Advisory, VDB Entry | |
References | () https://gitlab.com/libtiff/libtiff/-/commit/236b7191f04c60d09ee836ae13b50f812c841047 - Patch | |
References | () https://gitlab.com/libtiff/libtiff/-/issues/411 - Exploit, Patch, Third Party Advisory | |
References | () https://lists.debian.org/debian-lts-announce/2023/01/msg00018.html - Third Party Advisory | |
References | () https://security.netapp.com/advisory/ntap-20230110-0001/ - Third Party Advisory | |
References | () https://www.debian.org/security/2023/dsa-5333 - Third Party Advisory | |
CVSS |
v2 : v3 : |
v2 : unknown
v3 : 5.5 |
Information
Published : 2022-10-21 16:15
Updated : 2024-11-21 07:19
NVD link : CVE-2022-3627
Mitre link : CVE-2022-3627
CVE.ORG link : CVE-2022-3627
JSON object : View
Products Affected
debian
- debian_linux
libtiff
- libtiff
netapp
- active_iq_unified_manager
CWE
CWE-787
Out-of-bounds Write