Skip to content
Fencer Vulns
high 8.8

CVE-2018-14346 json

GNU Libextractor before 1.7 has a stack-based buffer overflow in ec_read_file_func (unzip.c).

published 2018-07-17 8 y ago modified 2026-06-17 4 mo ago also EUVD-2018-6267

cvss
8.8
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.1%
EPSS 2.1% chance of exploitation in 30 days, percentile 81%
public exploits
0
none known

Summary

GNU Libextractor before 1.7 has a stack-based buffer overflow in ec_read_file_func (unzip.c).

Patch / fix

  • gnu libextractor 1.7
  • libextractor Debian 14, Debian 13, Debian 12 1:1.7-1

debian advisories DEBIAN-CVE-2018-14346

  • libextractor Ubuntu 16.04 LTS 1:1.3-4+deb9u3build0.16.04.1
  • libextractor Ubuntu Pro 14.04 LTS 1:1.3-1ubuntu0.1~esm1

ubuntu advisories UBUNTU-CVE-2018-14346

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

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-2018-14346 updated cvss 4.3

libextractor: Stack-based buffer overflow in unzip.c:ec_read_file_func() allows for denial of service

  • Red Hat All currently supported Red Hat products
    not 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

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

Exploits and checks

  • lists.gnu.org http://lists.gnu.org/archive/html/bug-libextractor/2018-07/msg00001.html referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.0 8.8 CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD 2.0 6.8 AV:N/AC:M/Au:N/C:P/I:P/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.