LiveActive security incident?Get immediate response
CVE Record

CVE-2023-0804: LibTIFF 4.4.0 has an out-of-bounds write in tiffcrop in tools/tiffcrop.c:3609, allowing attackers to cause...

LibTIFF 4.4.0 has an out-of-bounds write in tiffcrop in tools/tiffcrop.c:3609, 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 33aee127.

MediumCVSS 6.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-0804 is a memory corruption flaw in LibTIFF’s tiffcrop tool. A crafted TIFF file can cause denial of service when processed. Business risk is highest for image-processing pipelines, document ingestion, or support workflows that accept untrusted TIFF files.

Executive priority

Treat as a moderate-priority reliability and ingestion-risk issue. Prioritize internet-facing or customer-facing file-processing environments first, then standard patching elsewhere. There is no provided evidence of active exploitation.

Technical view

LibTIFF <=4.4.0 has an out-of-bounds write in tools/tiffcrop.c around line 3609, tracked as CWE-787. The source bundle describes denial of service via crafted TIFF input, with CVSS 3.1 score 6.8 and high availability impact.

Likely exposure

Exposure is likely on systems with libtiff <=4.4.0 where tiffcrop is installed or invoked against untrusted TIFF files. The bundle does not prove exposure for every application merely linking LibTIFF.

Exploitation context

The provided sources do not indicate CISA KEV listing or active exploitation. Exploitation requires a crafted TIFF reaching vulnerable tiffcrop processing. The documented outcome is denial of service, with low integrity impact and no stated confidentiality impact.

Researcher notes

The vulnerability is specifically described in tiffcrop, not all LibTIFF consumers. Commit 33aee127 is cited as the source-level fix. Do not infer remote code execution or active exploitation from the provided evidence.

Mitigation direction

  • Upgrade to vendor-patched LibTIFF packages from your operating system or appliance vendor.
  • For source builds, ensure the build includes LibTIFF commit 33aee127 or a later vendor fix.
  • Avoid processing untrusted TIFF files with vulnerable tiffcrop versions.
  • Run image conversion workflows with least privilege and isolation where feasible.
  • Check Debian, Gentoo, Fedora, and NetApp advisories if those platforms apply.

Validation and detection

  • Inventory installed libtiff packages and tiffcrop binaries across servers and containers.
  • Confirm whether versions are <=4.4.0 or vendor-patched backports.
  • Identify workflows that process user-supplied or externally sourced TIFF files.
  • Verify patch status against the relevant vendor advisory, not version strings alone.
  • Review crash or availability incidents in TIFF-processing services.
Prepared
Confidence
high
Sources
8

Public sources used

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.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-0804 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:N/I:L/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
9Source 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:N/I:L/A:H2.54.2Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:L/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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
libtifflibtiff<=4.4.0Listed
Weakness

CWE details

CWE-787

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.

Open CWE intelligenceSame-CWE CVEs