Enterprise LinuxOperating system · Redhat
CVE-2023-3164
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 · uneditedA heap-buffer-overflow vulnerability was found in LibTIFF, in extractImageSection() at tools/tiffcrop.c:7916 and tools/tiffcrop.c:7801. This flaw allows attackers to cause a denial of service via a crafted tiff file.
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 · high confidenceHeap-buffer-overflow vulnerability in LibTIFF's tiffcrop tool in the extractImageSection() function at tools/tiffcrop.c:7916 and :7801. Processing a specially crafted malicious TIFF file can cause out-of-bounds memory read/write, leading to denial of service.
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
Enterprise LinuxOperating system
= 7.0= 8.0= 9.0< 4.6.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check if tiffcrop tool is installedRun 'which tiffcrop' or 'tiffcrop -h' to verify the tool exists on the systemAffected if tiffcrop is not installed - the vulnerability cannot be triggered
-
Determine installed LibTIFF library versionRun 'rpm -q libtiff' on RHEL systems, or check with your package manager. Alternatively, run 'tiffcrop -v' to see the tool version linkedAffected if The LibTIFF library or tiffcrop version is less than 4.6.0, or the version matches RHEL 7.0, 8.0, or 9.0 as listed
-
Identify the exact tiffcrop binary versionRun 'tiffcrop -v' to display the version information for the tiffcrop utilityAffected if Version output shows a version below 4.6.0 (e.g., 4.5.0, 4.4.1, etc.)
-
Verify TIFF library files on diskCheck the shared library version with 'ldd $(which tiffcrop)' and look for libtiff.so, or use 'rpm -qi libtiff' to confirm the installed package versionAffected if The libtiff library file shows a version string preceding 4.6.0
The environment is affected if tiffcrop is installed AND the LibTIFF library or tiffcrop version is below 4.6.0 (or matches RHEL 7.0/8.0/9.0 package versions).
Generated from the published advisory. Verify against your own configuration.
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.
dbcve · scoped4.6.0
Update LibTIFF to a version containing the fix for CVE-2023-3164. Until patched, avoid processing untrusted TIFF files with tiffcrop tool.
Libtiff 4.6.0
- Update the libtiff package to version 4.6.0 or later to resolve the heap-buffer-overflow vulnerability in extractImageSection()
- On Enterprise Linux systems, run: yum update libtiff or dnf update libtiff
- Verify the installed version after update: rpm -q libtiff
- Test the updated tiffcrop utility with the previously vulnerable workflows to confirm the fix
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Enterprise Linux
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-3164 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-3164 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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