CVE-2016-3177 json
Multiple use-after-free and double-free vulnerabilities in gifcolor.c in GIFLIB 5.1.2 have unspecified impact and attack vectors.
published 2017-01-23 9 y ago modified 2026-06-17 4 mo ago also EUVD-2016-4218
- cvss
- 9.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.6%
- EPSS 1.6% chance of exploitation in 30 days, percentile 76%
- public exploits
- 0
- none known
Summary
Multiple use-after-free and double-free vulnerabilities in gifcolor.c in GIFLIB 5.1.2 have unspecified impact and attack vectors.
Patch / fix
- giflib Debian 14, Debian 13, Debian 12 5.1.4-0.1
debian advisories DEBIAN-CVE-2016-3177
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2016-3177 updated cvss 3.3
giflib: Use-after-free in gifcolor utility
-
Red Hat Enterprise Linux 5 giflib Red Hat Enterprise Linux 6 giflib, giflib-utils Red Hat Enterprise Linux 7 giflib, giflib-utils Red Hat Enterprise Linux OpenStack Platform 7 (Kilo) Operational Tools phantomjs Red Hat OpenStack Platform 8 (Liberty) Operational Tools phantomjsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
1.63% chance of exploitation in the next 30 days, higher than 76% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 9.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
Classification
References
-
sourceforge.net
/p/giflib/bugs/83/
issue-tracking, patch
-
openwall.com
/lists/oss-security/2016/03/16/12
mailing-list, third-party-advisory
Sources
- CVE List CVE-2016-3177
- NVD CVE-2016-3177
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.