dbcve.org
Debian LinuxOperating system · Debian

CVE-2022-3599

MEDIUM · 6.5 CVSS v3.1 Published 2022-10-21
Fix available
A fix is available. Upgrade to after 4.4.0 or later.
See remediation →
72/100
Remediation priority · Elevated
Public exploit Remotely reachable No privileges Patch available

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 4.4.0 has an out-of-bounds read in writeSingleSection in tools/tiffcrop.c:7345, 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 e8131125.

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
How this class of weakness works · CWE-125

The code reads past the end (or before the start) of a buffer, returning memory that was never meant to be exposed. Attackers use it to leak secrets like keys or to defeat memory-protection defences. Remediation is validating indices and lengths before every read.

General guidance for the out-of-bounds read class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

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
Debian LinuxOperating system
Affected:= 10.0= 11.0
LibtiffApplication
Affected:<= 4.4.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

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 a release after 4.4.0
Vendor patch gitlab.com →
Recommended fix Moderate confidence

LibTIFF 4.4.1 or later (or the patched commit e8131125 for source builds); Debian security updates for libtiff 4.4.0-4.4.0-1+deb10u1 (buster) and 4.4.0-4.4.0-1+deb11u1 (bullseye)

  1. 1. Identify the libtiff version currently in use by running `tiffinfo -version` or checking the package manager: `dpkg -l | grep libtiff` on Debian systems
  2. 2. For source compilations: obtain the fixed libtiff source code by cloning the repository and checking out commit e8131125: `git clone https://gitlab.com/libtiff/libtiff.git && cd libtiff && git checkout e8131125`
  3. 3. Rebuild libtiff from the fixed source following standard build procedures (typically: `./configure && make && make install`)
  4. 4. For Debian systems: run `apt update && apt upgrade` to install the latest Debian security patches for the libtiff package
  5. 5. Verify the fix by checking the updated version: `tiffinfo -version` or `dpkg -l | grep libtiff`
  6. 6. Recompile any applications that link against libtiff to ensure they use the fixed library
Caveat Minimal risk - this is a bug fix for an out-of-bounds read; no API/ABI changes expected in point release

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

We can identify the exact fixed release, upgrade, and verify it in staging — typical engagement from $2,850. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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