LiveActive security incident?Get immediate response
CVE Record

CVE-2020-35521: A flaw was found in libtiff.

A flaw was found in libtiff. Due to a memory allocation failure in tif_read.c, a crafted TIFF file can lead to an abort, resulting in denial of service.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2020-35521 is a libtiff denial-of-service issue. A specially crafted TIFF image can make affected libtiff code abort while reading the file. The public bundle names libtiff 4.2.0 and does not provide CVSS scoring, confirmed active exploitation, or detailed fix versions.

Executive priority

Treat this as a targeted availability risk, not a known widespread compromise event based on the bundle. Prioritize internet-facing or business-critical image-processing systems first, then standard package remediation across managed endpoints and servers.

Technical view

The flaw is described as a memory allocation failure in libtiff's tif_read.c. Processing a crafted TIFF file can trigger an abort, causing denial of service. The bundle maps it to CWE-119 and identifies libtiff 4.2.0 as affected, with Fedora, Gentoo, Red Hat Bugzilla, and NetApp references.

Likely exposure

Exposure is most likely on systems or products using libtiff 4.2.0 to read TIFF files, especially where TIFF input comes from users, partners, email, uploads, or automated image-processing workflows.

Exploitation context

The provided sources do not show CISA KEV listing or confirmed active exploitation. The attack condition is crafted TIFF processing, so impact depends on whether affected software reads untrusted TIFF files and whether service restarts are automatic.

Researcher notes

Evidence is limited to a high-level flaw description and advisory references. No CVSS vector, exploit publication status, or exact fixed version is provided in the bundle. Validation should focus on libtiff 4.2.0 presence and untrusted TIFF parsing paths.

Mitigation direction

  • Inventory systems and applications that include libtiff or process TIFF files.
  • Check Fedora, Gentoo, Red Hat, NetApp, and relevant vendor guidance.
  • Apply vendor-provided libtiff package updates when available and applicable.
  • Restrict untrusted TIFF processing where patch status is uncertain.
  • Add monitoring for repeated image-processing crashes or service aborts.

Validation and detection

  • Confirm installed libtiff versions and vendor package provenance.
  • Identify services that parse TIFF files from external sources.
  • Review vendor advisories for affected package names and fixed builds.
  • Test that image-processing services remain stable after approved updates.
  • Verify crash logs no longer show tif_read.c-related abort behavior.
Prepared
Confidence
medium
Sources
6

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.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2020-35521 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

0CVSS vectors
0Timeline events
0ADP providers
5Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/alibtifflibtiff 4.2.0Listed
Weakness

CWE details

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.