dbcve.org
FedoraOperating system · Fedoraproject

CVE-2023-40745

MEDIUM · 6.5 CVSS v3.1 Published 2023-10-05
Fix available
A fix is available. Upgrade to 4.6.0 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable 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
LibTIFF is vulnerable to an integer overflow. This flaw allows remote attackers to cause a denial of service (application crash) or possibly execute an arbitrary code via a crafted tiff image, which triggers a heap-based buffer overflow.

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

LibTIFF contains an integer overflow vulnerability that can be triggered by processing a specially crafted TIFF image file. This integer overflow leads to a heap-based buffer overflow, potentially allowing remote attackers to cause a denial of service through application crash or possibly achieve arbitrary code execution.

MitigationUpdate LibTIFF to the latest patched version. Additionally, implement input validation on TIFF files before processing and apply the principle of least privilege to systems handling untrusted image files.

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
FedoraOperating system
Affected:all versions
Enterprise LinuxOperating system
Affected:= 8.0= 9.0
LibtiffApplication
Affected:< 4.6.0
Active Iq Unified ManagerApplication
Affected:all versions

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
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/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. Identify if LibTIFF library is installed
    Run package manager commands or scan for libtiff files (e.g., dpkg -l | grep libtiff, rpm -qa | grep libtiff, or find /usr/lib -name '*tiff*')
    Affected if LibTIFF library is present on the system
  2. Determine the installed LibTIFF version
    Query the library version using commands such as 'tiffinfo -version', 'tiff2pdf -v', or check the package version via package manager (e.g., rpm -q libtiff, dpkg -l libtiff*)
    Affected if The version returned is less than 4.6.0 or cannot be determined (indicating an older unpatched build)
  3. Check if running on affected Fedora or RHEL
    Verify the operating system and version using commands such as 'cat /etc/fedora-release' for Fedora or 'cat /etc/redhat-release' for RHEL
    Affected if Running any version of Fedora, or RHEL 8.0 or 9.0, with LibTIFF installed
  4. Identify if NetApp Active IQ Unified Manager is installed
    Check for NetApp Active IQ Unified Manager installation directories, services, or running processes (e.g., ps aux | grep -i 'active.iq' or looking for installation paths like /opt/netapp/ or /usr/local/activeiq*)
    Affected if NetApp Active IQ Unified Manager is installed, regardless of version
  5. Verify if TIFF file processing is in use
    Review application configurations, search for code that uses libtiff APIs (e.g., TIFFOpen, TIFFReadEncodedStrip), or check for applications that accept TIFF input
    Affected if Any application or service processes TIFF image files using the vulnerable LibTIFF library

The system is affected if LibTIFF with version less than 4.6.0 is installed and processes TIFF files, or if running NetApp Active IQ Unified Manager, or if running Fedora/RHEL with LibTIFF present.

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.

dbcve · scoped
Upgrade available Upgrade to 4.6.0 or later
Fixed in 4.6.0
Interim mitigation

Update LibTIFF to the latest patched version. Additionally, implement input validation on TIFF files before processing and apply the principle of least privilege to systems handling untrusted image files.

Recommended fix Moderate confidence

LibTIFF 4.6.0 or later

  1. Identify all systems running LibTIFF versions prior to 4.6.0
  2. For RHEL/CentOS/Enterprise Linux 8.0 and 9.0: Run 'dnf update libtiff' or 'yum update libtiff' to apply the latest available security patches
  3. For Fedora: Run 'dnf update libtiff' to apply the latest available packages
  4. For systems with Active IQ Unified Manager: Update the Unified Manager software to the latest version that includes the fixed LibTIFF library
  5. Verify the update was successful by running 'rpm -q libtiff' and confirming the version is 4.6.0 or later
  6. Restart any services that depend on the LibTIFF library to ensure the patched version is loaded

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Fedora Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-40745 — 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-40745 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