LibTIFF 4.3.0 has an out-of-bounds read in _TIFFmemcpy in tif_unix.c in certain situations involving a custom tag and 0x0200 as the second word of the DE field.
References
Configurations
Configuration 1 (hide)
|
Configuration 2 (hide)
|
Configuration 3 (hide)
|
History
21 Nov 2024, 06:47
Type | Values Removed | Values Added |
---|---|---|
References | () https://gitlab.com/libtiff/libtiff/-/issues/355 - Exploit, Mitigation, Third Party Advisory | |
References | () https://gitlab.com/libtiff/libtiff/-/merge_requests/287 - Exploit, Mitigation, Third Party Advisory | |
References | () https://lists.debian.org/debian-lts-announce/2022/03/msg00001.html - Mailing List, Third Party Advisory | |
References | () https://security.gentoo.org/glsa/202210-10 - Third Party Advisory | |
References | () https://security.netapp.com/advisory/ntap-20220311-0002/ - Third Party Advisory | |
References | () https://www.debian.org/security/2022/dsa-5108 - Third Party Advisory |
Information
Published : 2022-01-10 14:12
Updated : 2024-11-21 06:47
NVD link : CVE-2022-22844
Mitre link : CVE-2022-22844
CVE.ORG link : CVE-2022-22844
JSON object : View
Products Affected
netapp
- ontap_select_deploy_administration_utility
debian
- debian_linux
libtiff
- libtiff
CWE
CWE-125
Out-of-bounds Read