Skip to content
Fencer Intel
medium 5.5

CVE-2017-15922 json

In GNU Libextractor 1.4, there is an out-of-bounds read in the EXTRACTOR_dvi_extract_method function in plugins/dvi_extractor.c.

published 2017-10-26 9 y ago modified 2026-06-17 4 mo ago also EUVD-2017-7339

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

Summary

In GNU Libextractor 1.4, there is an out-of-bounds read in the EXTRACTOR_dvi_extract_method function in plugins/dvi_extractor.c.

Patch / fix

  • libextractor Debian 14, Debian 13, Debian 12 1:1.6-2

debian advisories DEBIAN-CVE-2017-15922

  • libextractor Ubuntu 16.04 LTS 1:1.3-4+deb9u3build0.16.04.1

ubuntu advisories UBUNTU-CVE-2017-15922

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

  • libextractor Arch Linux 1.6-1

arch linux advisories AVG-471

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-2017-15922 updated cvss 3.3

libextractor: Out of bounds read in the EXTRACTOR_dvi_extract_method function

  • 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

1.31% chance of exploitation in the next 30 days, higher than 70% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • lists.gnu.org http://lists.gnu.org/archive/html/bug-libextractor/2017-10/msg00008.html referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

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

Classification

Weakness

References

Sources

Fencer Intel 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.