LiveActive security incident?Get immediate response
CVE Record

CVE-2023-0797: LibTIFF 4.4.0 has an out-of-bounds read in tiffcrop in libtiff/tif_unix.c:368, invoked by tools/tiffcrop.c:...

LibTIFF 4.4.0 has an out-of-bounds read in tiffcrop in libtiff/tif_unix.c:368, invoked by tools/tiffcrop.c:2903 and tools/tiffcrop.c:6921, 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 afaabc3e.

MediumCVSS 6.8Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

A malicious TIFF processed by LibTIFF's tiffcrop tool can make the process read outside memory bounds and crash or deny service. Main business risk is disruption to services or workflows that process user-supplied TIFF files. Sources name LibTIFF <=4.4.0 and point to a fix commit and distro advisories.

Executive priority

Treat as a targeted remediation item for systems that process external TIFFs. It is not supported as actively exploited in the supplied sources, but denial of service can affect document ingestion, media pipelines, or automated conversion services.

Technical view

CVE-2023-0797 is a CWE-125 out-of-bounds read in the LibTIFF 4.4.0 tiffcrop path, involving libtiff/tif_unix.c and tools/tiffcrop.c. A crafted TIFF can trigger denial of service, with possible limited confidentiality impact per CVSS 3.1 score 6.8. Source-built users are directed to commit afaabc3e.

Likely exposure

Exposure is most likely where systems run LibTIFF or tiff tools at version 4.4.0 or earlier and process TIFF files from users, partners, email, uploads, batch jobs, or document conversion workflows. Packaged Linux distributions may have backported fixes under unchanged upstream version labels.

Exploitation context

The bundle does not show CISA KEV listing or other evidence of active exploitation. Exploitation requires a crafted TIFF reaching a vulnerable tiffcrop processing path. The cited impact is denial of service, not remote code execution.

Researcher notes

Focus validation on reachable tiffcrop use, not merely passive library presence. The provided CVSS vector is local, but the operational risk depends on whether remote users can cause server-side TIFF processing. Evidence names <=4.4.0 and a specific upstream fix commit.

Mitigation direction

  • Apply updated tiff/libtiff packages from Debian, Gentoo, or the relevant OS vendor.
  • For source builds, include upstream fix commit afaabc3e or upgrade beyond the affected release.
  • Limit processing of untrusted TIFF files until affected systems are updated.
  • Review image-processing services, converters, and batch jobs for tiffcrop or LibTIFF dependency use.

Validation and detection

  • Inventory servers, containers, and applications for LibTIFF or tiff tools version 4.4.0 or earlier.
  • Confirm whether vendor packages include the CVE-2023-0797 backport fix.
  • Identify workflows that accept untrusted TIFF files and invoke tiffcrop.
  • Verify patched builds against the upstream commit or distribution security advisory.
  • Check monitoring for crashes in TIFF-processing jobs after suspicious file submissions.
Prepared
Confidence
high
Sources
7

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-125: 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-2023-0797 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
Medium
CVSS
6.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H

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.

1CVSS vectors
0Timeline events
0ADP providers
7Source links

CVSS vector scores

1 official score

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.

ScoreVersionSeverityVectorExploitImpactSource
6.8CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H2.54.2Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.8Medium
CVSS 3.1 vector shape for CVE-2023-0797Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
libtifflibtiff<=4.4.0Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-125 · source CWE mapping

Out-of-bounds Read

Out-of-bounds Read represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.