Skip to content
Fencer Vulns
high 8.1

CVE-2017-6363 json

In the GD Graphics Library (aka LibGD) through 2.2.5, there is a heap-based buffer over-read in tiffWriter in gd_tiff.c.

published 2020-02-27 6 y ago modified 2026-06-17 4 mo ago also EUVD-2017-15424

cvss
8.1
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.4%
EPSS 1.4% chance of exploitation in 30 days, percentile 72%
public exploits
0
none known

Summary

In the GD Graphics Library (aka LibGD) through 2.2.5, there is a heap-based buffer over-read in tiffWriter in gd_tiff.c. NOTE: the vendor says "In my opinion this issue should not have a CVE, since the GD and GD2 formats are documented to be 'obsolete, and should only be used for development and testing purposes.'

Patch / fix

  • libgd2 Debian 14, Debian 13, Debian 12 2.3.0-1

debian advisories DEBIAN-CVE-2017-6363

  • libgd2 Ubuntu 18.04 LTS 2.2.5-4ubuntu0.5
  • libgd2 Ubuntu 20.04 LTS 2.2.5-5.2ubuntu2.1
  • libgd2 Ubuntu Pro 14.04 LTS 2.1.0-3ubuntu0.11+esm2
  • libgd2 Ubuntu Pro 16.04 LTS 2.1.1-4ubuntu0.16.04.12+esm1

ubuntu advisories UBUNTU-CVE-2017-6363

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • gd Alpine 3.11 2.2.5-r4
  • gd Alpine 3.24, Alpine 3.23, Alpine 3.22 +10 more 2.3.0-r0

alpine advisories ALPINE-CVE-2017-6363

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Exploit prediction

1.40% chance of exploitation in the next 30 days, higher than 72% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • github.com https://github.com/libgd/libgd/issues/383 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 8.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:H
NVD 2.0 5.8 AV:N/AC:M/Au:N/C:P/I:N/A:P

Classification

Weakness

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.