CVE-2023-52355: Libtiff: tiffrasterscanlinesize64 produce too-big size and could cause oom
An out-of-memory flaw was found in libtiff that could be triggered by passing a crafted tiff file to the TIFFRasterScanlineSize64() API. This flaw allows a remote attacker to cause a denial of service via a crafted input with a size smaller than 379 KB.
Security readout for executives and security teams
Plain-English summary
CVE-2023-52355 is a denial-of-service flaw in libtiff. A specially crafted TIFF file, reportedly under 379 KB, can cause excessive memory use when processed through TIFFRasterScanlineSize64(). Business impact is service disruption where systems automatically ingest or process TIFF images.
Executive priority
Prioritize remediation for internet-facing or automated image-processing systems. This is not described as data theft or code execution, but it can disrupt services with small crafted files.
Technical view
The flaw affects libtiff’s TIFFRasterScanlineSize64() API, which can calculate an excessively large size and trigger out-of-memory conditions. Red Hat lists affected libtiff packages across RHEL 8, RHEL 9, RHEL 10, and some Red Hat AI Inference Server and Discovery container packages. CVSS is 7.5, network attack vector, availability impact only.
Likely exposure
Highest exposure is in servers, applications, containers, or workflows that accept TIFF files from users, partners, email, web uploads, scanners, or automated image pipelines.
Exploitation context
The public sources describe crafted-file denial of service. The provided data does not show CISA KEV listing or confirmed active exploitation. No exploit code or operational attack details are provided here.
Researcher notes
Evidence is strongest for Red Hat-packaged libtiff and referenced Red Hat product containers. The bundle does not provide fixed versions or detailed upstream patch metadata. Treat non-Red Hat exposure as possible where libtiff uses the affected API, pending vendor confirmation.
Mitigation direction
Apply applicable Red Hat security advisories for affected products and packages.
Update libtiff or dependent container images through vendor-supported channels.
Inventory applications that process TIFF files automatically or from untrusted sources.
Limit untrusted TIFF ingestion where updates cannot be applied promptly.
Check upstream libtiff issue and vendor guidance for non-Red Hat environments.
Validation and detection
Identify installed libtiff and compat-libtiff3 package versions across Linux assets.
Check Red Hat advisories for product-specific affected and fixed package guidance.
Review container base images for bundled libtiff packages.
Confirm TIFF-processing services remain stable after vendor updates.
Monitor memory-exhaustion alerts in image-processing workflows.
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-787: 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-787 · source CWE mapping
Out-of-bounds Write
Out-of-bounds Write represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.