dbcve.org
LibtiffApplication

CVE-2023-30775

MEDIUM · 5.5 CVSS v3.1 Published 2023-05-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability was found in the libtiff library. This security flaw causes a heap buffer overflow in extractContigSamples32bits, tiffcrop.c.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A heap buffer overflow vulnerability exists in the extractContigSamples32bits function within tiffcrop.c of the libtiff library. This flaw allows processing of malformed TIFF images to trigger heap memory corruption, potentially leading to application crashes or potentially arbitrary code execution depending on exploitation context.

MitigationUpdate libtiff to the latest version when a patch becomes available. Avoid processing untrusted TIFF files with tiffcrop until the vulnerability is patched.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
LibtiffApplication
Affected:= 4.4.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if libtiff is installed
    Run `pkg-config --modversion libtiff-4` or check your package manager for libtiff installation status (e.g., `dpkg -l | grep libtiff` on Debian-based systems, `rpm -qa | grep libtiff` on RHEL-based systems)
    Affected if libtiff is not installed or the package cannot be found
  2. Identify the installed libtiff version
    Run `tiffinfo -version` or `tiffcrop -v` to display the version information. Alternatively, check the shared library version with `ldd $(which tiffcrop) | grep tiff`
    Affected if The displayed version is 4.4.0 exactly
  3. Verify tiffcrop utility availability
    Confirm the tiffcrop binary exists and is executable by running `which tiffcrop`
    Affected if tiffcrop is present on the system and the libtiff version is 4.4.0
  4. Confirm library linkage
    Run `ldconfig -p | grep libtiff` to list the libtiff library version currently loaded by the system
    Affected if The linked library version resolves to 4.4.0

A system is affected if libtiff version 4.4.0 is installed and the tiffcrop utility is available for processing TIFF files.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update libtiff to the latest version when a patch becomes available. Avoid processing untrusted TIFF files with tiffcrop until the vulnerability is patched.

Fix this in Libtiff Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-30775 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-30775 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data