CVE-2022-3599
published 2022-10-21CVE-2022-3599: LibTIFF 4.4.0 has an out-of-bounds read in writeSingleSection in tools/tiffcrop.c:7345, allowing attackers to cause a denial-of-service via a crafted tiff…
PriorityP424medium6.5CVSS 3.1
AVNACLPRNUIRSUCNINAH
EPSS
0.95%
56.7th percentile
LibTIFF 4.4.0 has an out-of-bounds read in writeSingleSection in tools/tiffcrop.c:7345, 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 e8131125.
Affected
7 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | debian_linux | — | — |
| debian | debian_linux | — | — |
| debian | tiff | < tiff 4.4.0-5 (bookworm) | tiff 4.4.0-5 (bookworm) |
| libtiff | libtiff | <= 4.4.0 | — |
| libtiff | libtiff | — | — |
| msrc | cbl2_libtiff_4.4.0-6_on_cbl_mariner_2.0 | — | — |
| msrc | cm1_libtiff_4.4.0-5_on_cbl_mariner_1.0 | — | — |
CVSS provenance
nvdv3.16.5MEDIUMCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
osv6.5MEDIUM
vendor_msrc6.5MEDIUM
vendor_ubuntu6.5MEDIUM
vendor_debian5.5MEDIUM
vendor_redhat5.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
OSV
tiff vulnerabilities
osv·2022-11-08·CVSS 6.5
CVE-2022-2519 [MEDIUM] tiff vulnerabilities
tiff vulnerabilities
It was discovered that LibTIFF incorrectly handled certain memory operations
when using tiffcrop. An attacker could trick a user into processing a specially
crafted tiff image file and potentially use this issue to cause a denial of
service. This issue only affected Ubuntu 22.10. (CVE-2022-2519, CVE-2022-2520,
CVE-2022-2521, CVE-2022-2953)
It was discovered that LibTIFF did not properly perform bounds checking in
certain operations when using tiffcrop. An attacker could trick a user into
processing a specially crafted tiff image file and potentially use this issue
to allow for information disclosure or to cause the application to crash. This
issue only affected to Ubuntu 18.04 LTS, Ubuntu 20.04 LTS and Ubuntu 22.04 LTS.
(CVE-2022-2867, CVE-2022-2868, CVE-2022-2869)
OSV
CVE-2022-3599: LibTIFF 4
osv·2022-10-21·CVSS 6.5
CVE-2022-3599 [MEDIUM] CVE-2022-3599: LibTIFF 4
LibTIFF 4.4.0 has an out-of-bounds read in writeSingleSection in tools/tiffcrop.c:7345, 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 e8131125.
GHSA
GHSA-6cg2-4798-gw4g: LibTIFF 4
ghsa_unreviewed·2022-10-21
CVE-2022-3599 [MEDIUM] CWE-125 GHSA-6cg2-4798-gw4g: LibTIFF 4
LibTIFF 4.4.0 has an out-of-bounds read in writeSingleSection in tools/tiffcrop.c:7345, 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 e8131125.
Red Hat
kernel: bonding: fix missed rcu protection
vendor_redhat·2025-02-26·CVSS 5.5
CVE-2022-49456 [MEDIUM] CWE-413 kernel: bonding: fix missed rcu protection
kernel: bonding: fix missed rcu protection
In the Linux kernel, the following vulnerability has been resolved:
bonding: fix missed rcu protection
When removing the rcu_read_lock in bond_ethtool_get_ts_info() as
discussed [1], I didn't notice it could be called via setsockopt,
which doesn't hold rcu lock, as syzbot pointed:
stack backtrace:
CPU: 0 PID: 3599 Comm: syz-executor317 Not tainted 5.18.0-rc5-syzkaller-01392-g01f4685797a5 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106
bond_option_active_slave_get_rcu include/net/bonding.h:353 [inline]
bond_ethtool_get_ts_info+0x32c/0x3a0 drivers/net/bonding/bond_main.c:5595
__ethtool_get_ts_info+0x173/
Red Hat
kernel: watch_queue: Fix NULL dereference in error cleanup
vendor_redhat·2025-02-26·CVSS 5.5
CVE-2022-49257 [MEDIUM] kernel: watch_queue: Fix NULL dereference in error cleanup
kernel: watch_queue: Fix NULL dereference in error cleanup
In the Linux kernel, the following vulnerability has been resolved:
watch_queue: Fix NULL dereference in error cleanup
In watch_queue_set_size(), the error cleanup code doesn't take account of
the fact that __free_page() can't handle a NULL pointer when trying to free
up buffer pages that did get allocated.
Fix this by only calling __free_page() on the pages actually allocated.
Without the fix, this can lead to something like the following:
BUG: KASAN: null-ptr-deref in __free_pages+0x1f/0x1b0 mm/page_alloc.c:5473
Read of size 4 at addr 0000000000000034 by task syz-executor168/3599
...
Call Trace:
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106
__kasan_report mm/kasan/report.c:446 [inline]
Ubuntu
LibTIFF vulnerabilities
vendor_ubuntu·2022-11-08·CVSS 6.5
CVE-2022-2869 [MEDIUM] LibTIFF vulnerabilities
Title: LibTIFF vulnerabilities
Summary: Several security issues were fixed in LibTIFF.
It was discovered that LibTIFF incorrectly handled certain memory operations
when using tiffcrop. An attacker could trick a user into processing a specially
crafted tiff image file and potentially use this issue to cause a denial of
service. This issue only affected Ubuntu 22.10. (CVE-2022-2519, CVE-2022-2520,
CVE-2022-2521, CVE-2022-2953)
It was discovered that LibTIFF did not properly perform bounds checking in
certain operations when using tiffcrop. An attacker could trick a user into
processing a specially crafted tiff image file and potentially use this issue
to allow for information disclosure or to cause the application to crash. This
issue only affected to Ubuntu 18.04 LTS, Ubuntu 20.04 LTS an
Microsoft
LibTIFF 4.4.0 has an out-of-bounds read in writeSingleSection in tools/tiffcrop.c:7345 allowing attackers to cause a denial-of-service via a crafted tiff file. For users that compile libtiff from sour
vendor_msrc·2022-10-11·CVSS 6.5
CVE-2022-3599 [MEDIUM] CWE-125 LibTIFF 4.4.0 has an out-of-bounds read in writeSingleSection in tools/tiffcrop.c:7345 allowing attackers to cause a denial-of-service via a crafted tiff file. For users that compile libtiff from sour
LibTIFF 4.4.0 has an out-of-bounds read in writeSingleSection in tools/tiffcrop.c:7345 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 e8131125.
FAQ: Is Azure Linux the only Microsoft product that includes this open-source library and is therefore potentially affected by this vulnerability?
One of the main benefits to our customers who choose to use the Azure Linux distro is the commitment to keep it up to date with the most recent and most secure versions of the open source libraries with which the distro is composed. Microsoft is committed to transparency in this work which is why we began publishing CSAF/VEX in October 2025. See this blog post for more information. If impact to additio
Red Hat
libtiff: out-of-bounds read in writeSingleSection in tools/tiffcrop.c
vendor_redhat·2022-02-25·CVSS 5.5
CVE-2022-3599 [MEDIUM] libtiff: out-of-bounds read in writeSingleSection in tools/tiffcrop.c
libtiff: out-of-bounds read in writeSingleSection in tools/tiffcrop.c
LibTIFF 4.4.0 has an out-of-bounds read in writeSingleSection in tools/tiffcrop.c:7345, 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 e8131125.
An out-of-bounds read flaw was found in the writeSingleSection function in tools/tiffcrop.c in the libtiff package. By persuading a victim to open a specially-crafted TIFF image file, a remote attacker could cause a denial of service condition.
Package: libtiff (Red Hat Enterprise Linux 6) - Out of support scope
Package: compat-libtiff3 (Red Hat Enterprise Linux 7) - Out of support scope
Package: libtiff (Red Hat Enterprise Linux 7) - Out of support scope
Package: compat
Debian
CVE-2022-3599: tiff - LibTIFF 4.4.0 has an out-of-bounds read in writeSingleSection in tools/tiffcrop....
vendor_debian·2022·CVSS 5.5
CVE-2022-3599 [MEDIUM] CVE-2022-3599: tiff - LibTIFF 4.4.0 has an out-of-bounds read in writeSingleSection in tools/tiffcrop....
LibTIFF 4.4.0 has an out-of-bounds read in writeSingleSection in tools/tiffcrop.c:7345, 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 e8131125.
Scope: local
bookworm: resolved (fixed in 4.4.0-5)
bullseye: resolved (fixed in 4.2.0-1+deb11u3)
forky: resolved (fixed in 4.4.0-5)
sid: resolved (fixed in 4.4.0-5)
trixie: resolved (fixed in 4.4.0-5)
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2022-49257 kernel: watch_queue: Fix NULL dereference in error cleanup
bugzilla·2025-02-26·CVSS 5.5
CVE-2022-49257 [MEDIUM] CVE-2022-49257 kernel: watch_queue: Fix NULL dereference in error cleanup
CVE-2022-49257 kernel: watch_queue: Fix NULL dereference in error cleanup
In the Linux kernel, the following vulnerability has been resolved:
watch_queue: Fix NULL dereference in error cleanup
In watch_queue_set_size(), the error cleanup code doesn't take account of
the fact that __free_page() can't handle a NULL pointer when trying to free
up buffer pages that did get allocated.
Fix this by only calling __free_page() on the pages actually allocated.
Without the fix, this can lead to something like the following:
BUG: KASAN: null-ptr-deref in __free_pages+0x1f/0x1b0 mm/page_alloc.c:5473
Read of size 4 at addr 0000000000000034 by task syz-executor168/3599
...
Call Trace:
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106
__kasan_report mm/kasan/r
Bugzilla
CVE-2022-49456 kernel: bonding: fix missed rcu protection
bugzilla·2025-02-26·CVSS 5.5
CVE-2022-49456 [MEDIUM] CVE-2022-49456 kernel: bonding: fix missed rcu protection
CVE-2022-49456 kernel: bonding: fix missed rcu protection
In the Linux kernel, the following vulnerability has been resolved:
bonding: fix missed rcu protection
When removing the rcu_read_lock in bond_ethtool_get_ts_info() as
discussed [1], I didn't notice it could be called via setsockopt,
which doesn't hold rcu lock, as syzbot pointed:
stack backtrace:
CPU: 0 PID: 3599 Comm: syz-executor317 Not tainted 5.18.0-rc5-syzkaller-01392-g01f4685797a5 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106
bond_option_active_slave_get_rcu include/net/bonding.h:353 [inline]
bond_ethtool_get_ts_info+0x32c/0x3a0 drivers/net/bonding/bond_main.c:5595
__ethtool_
Bugzilla
CVE-2022-3599 libtiff: out-of-bounds read in writeSingleSection in tools/tiffcrop.c
bugzilla·2022-11-15·CVSS 6.5
CVE-2022-3599 [MEDIUM] CVE-2022-3599 libtiff: out-of-bounds read in writeSingleSection in tools/tiffcrop.c
CVE-2022-3599 libtiff: out-of-bounds read in writeSingleSection in tools/tiffcrop.c
LibTIFF 4.4.0 has an out-of-bounds read in writeSingleSection in tools/tiffcrop.c:7345, 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 e8131125.
References:
https://gitlab.com/libtiff/libtiff/-/commit/e813112545942107551433d61afd16ac094ff246
https://gitlab.com/libtiff/libtiff/-/issues/398
https://gitlab.com/gitlab-org/cves/-/blob/master/2022/CVE-2022-3599.json
Discussion:
Created libtiff tracking bugs for this issue:
Affects: fedora-all [bug 2148888]
---
This issue has been addressed in the following products:
Red Hat Enterprise Linux 9
Via RHSA-2023:2340 https://access.redhat.com/errata/RHSA-202
https://gitlab.com/gitlab-org/cves/-/blob/master/2022/CVE-2022-3599.jsonhttps://gitlab.com/libtiff/libtiff/-/commit/e813112545942107551433d61afd16ac094ff246https://gitlab.com/libtiff/libtiff/-/issues/398https://lists.debian.org/debian-lts-announce/2023/01/msg00018.htmlhttps://security.netapp.com/advisory/ntap-20230110-0001/https://www.debian.org/security/2023/dsa-5333https://gitlab.com/gitlab-org/cves/-/blob/master/2022/CVE-2022-3599.jsonhttps://gitlab.com/libtiff/libtiff/-/commit/e813112545942107551433d61afd16ac094ff246https://gitlab.com/libtiff/libtiff/-/issues/398https://lists.debian.org/debian-lts-announce/2023/01/msg00018.htmlhttps://security.netapp.com/advisory/ntap-20230110-0001/https://www.debian.org/security/2023/dsa-5333
2022-10-21
Published