CVE-2025-61143
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 · uneditedlibtiff up to v4.7.1 was discovered to contain a NULL pointer dereference via the component libtiff/tif_open.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 confidenceA NULL pointer dereference vulnerability exists in libtiff's tif_open.c component, allowing attackers to cause a denial of service via a specially crafted TIFF file that triggers the NULL dereference during file opening operations.
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< 4.7.1CVSS 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 installed libtiff versionRun 'tiffinfo -version' or check the library file (e.g., /usr/lib/libtiff.so.5 or .so.6) using 'pkg-config --modversion libtiff-4' or 'ldd' on linked binariesAffected if Version returned is less than 4.7.1
-
Identify applications using libtiffRun 'ldd /path/to/binary | grep tiff' on suspected TIFF-processing applications (e.g., ImageMagick, GDAL, browsers) to see if they link against libtiffAffected if The application links to a libtiff version less than 4.7.1
-
Check for tif_open.c usage in custom codeSearch source code repositories for '#include tif_open.h' or calls to TIFFOpen(), TIFFClientOpen(), or related file-opening functions from libtiffAffected if Code uses libtiff file-opening functions and the linked library version is below 4.7.1
You are affected if any libtiff installation or application linked to libtiff in your environment has a version lower than 4.7.1, since the NULL pointer dereference triggers during TIFF file opening operations.
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.7.1
Upgrade libtiff to the latest version beyond v4.7.1 to obtain the vendor patch, and validate all TIFF files processed by applications using libtiff.
Libtiff 4.7.1 or later (upgrade to latest stable release)
- 1. Identify all applications and systems that link against the libtiff library
- 2. Verify current installed libtiff version using 'tiffinfo -version' or by checking package manager
- 3. Upgrade libtiff to version 4.7.1 or later using your system's package manager (e.g., 'apt-get install libtiff-dev', 'yum update tiff', or 'brew upgrade libtiff')
- 4. Rebuild any applications that statically link against libtiff after the upgrade
- 5. Verify the new version is installed and the vulnerability is resolved by running 'tiffinfo -version'
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-61143 — 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-2025-61143 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