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.
Security readout for executives and security teams
Plain-English summary
CVE-2023-3576 is a denial-of-service issue in libtiff's tiffcrop utility. If a user or automated process opens a specially crafted TIFF with tiffcrop, the tool can leak memory and crash. The business impact is service disruption in image-processing workflows, not data theft or system takeover based on the supplied sources.
Executive priority
Treat this as a moderate operational reliability issue. Prioritize patching servers or workstations that process external TIFF files, especially automated conversion pipelines, but it does not appear to justify emergency incident response from the supplied evidence.
Technical view
The flaw is a memory leak in tiffcrop.c affecting libtiff/tiffcrop. Red Hat rates it CVSS 3.1 score 5.5: local attack vector, low complexity, no privileges, user interaction required, and high availability impact. Sources describe crash potential from crafted TIFF input; they do not document confidentiality or integrity impact.
Likely exposure
Exposure is most likely on systems where tiffcrop is installed and processes untrusted TIFF files, including listed Red Hat Enterprise Linux libtiff-related packages. Risk is lower where tiffcrop is absent, unused, or only handles trusted images.
Exploitation context
The source bundle does not show CISA KEV listing or active exploitation evidence. Exploitation requires a crafted TIFF to be passed to tiffcrop, likely through user action or an automated image-processing workflow.
Researcher notes
Evidence is strongest for Red Hat-packaged libtiff components and the tiffcrop utility. The bundle lists some RHEL 6/7 statuses as unknown, so validate against vendor advisories. No exploit code, active exploitation, or universal upstream fixed version is provided in the supplied material.
Mitigation direction
Apply vendor-provided libtiff updates from Red Hat or your distribution.
Check Red Hat RHSA-2023:6575 and vendor CVE guidance for fixed package availability.
Avoid processing untrusted TIFF files with tiffcrop until patched.
Restrict automated tiffcrop workflows to trusted sources where feasible.
Monitor distribution advisories for Debian and other maintained platforms.
Validation and detection
Inventory systems with libtiff, compat-libtiff3, mingw-libtiff, or tiffcrop installed.
Identify workflows that invoke tiffcrop on user-supplied TIFF files.
Confirm installed packages match vendor-fixed versions or advisories.
Review crash, memory, or job-failure logs around TIFF processing.
Prioritize RHEL 8 and RHEL 9 packages marked affected in the bundle.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-119: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-119 · source CWE mapping
Improper Restriction of Operations within the Bounds of a Memory Buffer
Improper Restriction of Operations within the Bounds of a Memory Buffer represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.