CVE-2017-15602: In GNU Libextractor 1.4, there is an integer signedness error for the chunk size in the EXTRACTOR_nsfe_extract

This week

HIGH 7.5REMOTEDOWNGRADE

CVE-2017-15602 is a high-severity flaw (CVSS 7.5) affecting libextractor. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

In GNU Libextractor 1.4, there is an integer signedness error for the chunk size in the EXTRACTOR_nsfe_extract_method function in plugins/nsfe_extractor.c, leading to an infinite loop for a crafted size.

Why this priority

High severity
Public exploit reference
Remotely exploitable, no login, no user action

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	1.5% (top 26%)
CISA exploited list	No
Weakness	CWE-835
Published	2017-10-18
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: gnu

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2017-10-18 21:29 UTCPublished CVE record published
2026-06-17 01:07 UTCUpdated Record last modified

gnu libextractor DOWNGRADE

Affected: 1.4

Fixed in: no fixed release known

Safe to downgrade to: a release before 1.4

1. Check installed version

apt-cache policy libextractor || rpm -q libextractor || libextractor --version

2. No fixed release: DOWNGRADE to a release before 1.4 (Debian / Ubuntu)

apt-cache madison libextractor sudo apt install libextractor=<VERSION_BEFORE_1.4> sudo apt-mark hold libextractor

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list libextractor sudo dnf downgrade libextractor-<VERSION_BEFORE_1.4> sudo dnf versionlock add libextractor

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2017-15602?

libextractor: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2017-15602 being exploited?

CVE-2017-15602 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2017-15602 affect?

CVE-2017-15602 affects libextractor. Severity is high (CVSS 7.5). In GNU Libextractor 1.4, there is an integer signedness error for the chunk size in the EXTRACTOR_nsfe_extract_method function in plugins/nsfe_extractor.c, leading to an infinite loop for a crafted size.

How urgent is CVE-2017-15602?

Priority 55/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

Related CVEs

CVE-2019-15531 MEDIUM 6.5 UPGRADE MITIGATE GNU Libextractor through 1.9 has a heap-based buffer over-read in the function EXTRACTOR_dvi_extract_method in
CVE-2018-20431 MEDIUM 6.5 UPGRADE MITIGATE GNU Libextractor through 1.8 has a NULL Pointer Dereference vulnerability in the function process_metadata() i
CVE-2018-20430 MEDIUM 6.5 UPGRADE MITIGATE GNU Libextractor through 1.8 has an out-of-bounds read vulnerability in the function history_extract() in plug
CVE-2018-16430 HIGH 8.8 UPGRADE MITIGATE GNU Libextractor through 1.7 has an out-of-bounds read vulnerability in EXTRACTOR_zip_extract_method() in zip_
CVE-2018-14347 MEDIUM 6.5 MITIGATE UPGRADE GNU Libextractor before 1.7 contains an infinite loop vulnerability in EXTRACTOR_mpeg_extract_method (mpeg_ext

References

← Back to latest CVEs