CVE-2023-3576 json
Libtiff: memory leak in tiffcrop.c
published 2023-10-04 3 y ago modified 2026-11-07 44 h ago also EUVD-2023-44226 , JLSEC-2025-310
- cvss
- 5.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 24%
- public exploits
- 0
- none known
Summary
A memory leak flaw was found in Libtiff's tiffcrop utility. This issue occurs when tiffcrop operates on a TIFF image file, allowing an attacker to pass a crafted TIFF image file to tiffcrop utility, which causes this memory leak issue, resulting an application crash, eventually leading to a denial of service.
Patch / fix
- julia Libtiff_jll 4.5.1+0
- Red Hat Red Hat Enterprise Linux 9 0:4.4.0-10.el9
- tiff Debian 12 4.5.0-6+deb12u1
- tiff Debian 14, Debian 13 4.5.1~rc3-1
debian advisories DEBIAN-CVE-2023-3576
- tiff Ubuntu 20.04 LTS 4.1.0+git191117-2ubuntu0.20.04.11
- tiff Ubuntu 22.04 LTS 4.3.0-6ubuntu0.7
- tiff Ubuntu Pro 14.04 LTS 4.0.3-7ubuntu0.11+esm11
- tiff Ubuntu Pro 16.04 LTS 4.0.6-1ubuntu0.8+esm14
- tiff Ubuntu Pro 18.04 LTS 4.0.9-5ubuntu0.10+esm4
ubuntu advisories UBUNTU-CVE-2023-3576
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- libtiff RHEL 9 4.4.0-10.el9
- libtiff-tools RHEL 9 4.4.0-10.el9
red hat advisories RHSA-2023:6575
- tiff SLES for SAP 12 SP5, SLES 12 SP5, SLE Software Development Kit 12 SP5 4.0.9-44.71.1
- tiff SLE Module for Package Hub 15 SP5, SLE Module for Package Hub 15 SP4, SLE Module for Basesystem 15 SP5 +9 more 4.0.9-150000.45.32.1
suse advisories SUSE-SU-2023:4371-1SUSE-SU-2023:4370-1
- libtiff AlmaLinux 9 4.4.0-10.el9
- libtiff-tools AlmaLinux 9 4.4.0-10.el9
almalinux advisories ALSA-2023:6575
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-2023-3576 updated cvss 5.5
libtiff: memory leak in tiffcrop.c
-
Red Hat Enterprise Linux 6 libtiff Red Hat Enterprise Linux 7 libtiff, libtiff-tools, compat-libtiff3affected: no fix planned “Out of support scope”
-
Red Hat Enterprise Linux 8 libtiff, libtiff-tools, mingw-libtiff, compat-libtiff3, mingw32-libtiff, mingw64-libtiffaffected: no fix planned “Will not fix”
-
Red Hat Enterprise Linux 9 compat-libtiff3affected: no fix available
-
Red Hat CodeReady Linux Builder (v. 9) libtiff-tools 4.4.0-10.el9 Red Hat Enterprise Linux AppStream (v. 9) libtiff 4.4.0-10.el9fixed: vendor fix RHSA-2023:6575
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
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 17 mo ago
Exploit prediction
0.32% chance of exploitation in the next 30 days, higher than 24% of all scored CVEs (FIRST EPSS, 2026-11-08).
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 |
| 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.5.1+0 |
4.5.1+0 |
Affected products
- Red Hat Red Hat Enterprise Linux 9
- Red Hat Red Hat Enterprise Linux 6
- Red Hat Red Hat Enterprise Linux 7
- Red Hat Red Hat Enterprise Linux 8
Classification
References
-
access.redhat.com
/errata/RHSA-2023:6575
vendor-advisory, web
-
access.redhat.com
/security/cve/CVE-2023-3576
vdb-entry, third-party-advisory, web
-
bugzilla.redhat.com
/show_bug.cgi?id=2219340
issue-tracking, third-party-advisory, web
-
lists.debian.org
/debian-lts-announce/2024/03/msg00011.html
web
Sources
- CVE List CVE-2023-3576
- NVD CVE-2023-3576
- OSV JLSEC-2025-310
Fencer Vulns 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.