How severe is CVE-2016-3623?

CVE-2016-3623 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability high.

Is CVE-2016-3623 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 6% (92nd percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2016-3623?

CVE-2016-3623 primarily affects Libtiff. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2016-3623?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2016-3623 published?

CVE-2016-3623 was published on 2016-10-03 and last updated on 2026-06-17.

CVE-2016-3623

CVE-2016-3623 is a high-severity vulnerability in Libtiff with a CVSS 3.x base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-369.

Key facts

Severity: High (CVSS 3.x base score 7.5)
CVSS v2: 5.0
EPSS exploit prediction: 6% (92nd percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-369
Affected product: Libtiff
Published: 2016-10-03
Last modified: 2026-06-17

Description

The rgb2ycbcr tool in LibTIFF 4.0.6 and earlier allows remote attackers to cause a denial of service (divide-by-zero) by setting the (1) v or (2) h parameter to 0.

Frequently asked questions

What is CVE-2016-3623?: The rgb2ycbcr tool in LibTIFF 4.0.6 and earlier allows remote attackers to cause a denial of service (divide-by-zero) by setting the (1) v or (2) h parameter to 0.
How severe is CVE-2016-3623?: CVE-2016-3623 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability high.
Is CVE-2016-3623 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 6% (92nd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2016-3623?: CVE-2016-3623 primarily affects Libtiff. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2016-3623?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2016-3623 published?: CVE-2016-3623 was published on 2016-10-03 and last updated on 2026-06-17.

References

Affected products (2)

cpe:2.3:a:libtiff:libtiff:*:*:*:*:*:*:*:*
cpe:2.3:o:opensuse:opensuse:13.2:*:*:*:*:*:*:*

More vulnerabilities in Libtiff

CVE-2004-0929 — Critical (CVSS 10.0): Heap-based buffer overflow in the OJPEGVSetField function in tif_ojpeg.c for libtiff 3.6.1 and earlier, when compiled…
CVE-2004-1308 — Critical (CVSS 10.0): Integer overflow in (1) tif_dirread.c and (2) tif_fax3.c for libtiff 3.5.7 and 3.7.0 allows remote attackers to execute…
CVE-2016-9540 — Critical (CVSS 9.8): tools/tiffcp.c in libtiff 4.0.6 has an out-of-bounds write on tiled images with odd tile width versus image width.…
CVE-2016-9539 — Critical (CVSS 9.8): tools/tiffcrop.c in libtiff 4.0.6 has an out-of-bounds read in readContigTilesIntoBuffer(). Reported as MSVR 35092.
CVE-2016-9538 — Critical (CVSS 9.8): tools/tiffcrop.c in libtiff 4.0.6 reads an undefined buffer in readContigStripsIntoBuffer() because of a uint16 integer…
CVE-2016-9537 — Critical (CVSS 9.8): tools/tiffcrop.c in libtiff 4.0.6 has out-of-bounds write vulnerabilities in buffers. Reported as MSVR 35093, MSVR…

All CVEs affecting Libtiff →

Other CWE-369 (Divide By Zero) vulnerabilities

CVE-2021-32494 — Critical (CVSS 10.0): Radare2 has a division by zero vulnerability in Mach-O parser's rebase_buffer function. This allow attackers to create…
CVE-2017-11720 — Critical (CVSS 9.8): There is a division-by-zero vulnerability in LAME 3.99.5, caused by a malformed input file.
CVE-2020-20892 — High (CVSS 8.8): An issue was discovered in function filter_frame in libavfilter/vf_lenscorrection.c in Ffmpeg 4.2.1, allows attackers…
CVE-2025-4637 — High (CVSS 8.7): Divide By Zero vulnerability in davisking dlib allows remote attackers to cause a denial of service via a crafted…
CVE-2026-37232 — High (CVSS 8.6): An issue was discovered in OpenAirInterface5G 2.4.0 (nr-softmodem) in the E2SM-KPM RAN Function's PRB utilization…
CVE-2024-26945 — High (CVSS 8.4): In the Linux kernel, the following vulnerability has been resolved: crypto: iaa - Fix nr_cpus < nr_iaa case If…

Browse all CWE-369 (Divide By Zero) vulnerabilities →