Skip to content
Fencer Intel
medium 5.5

CVE-2017-9870 json

The III_i_stereo function in layer3.c in mpglib, as used in libmpgdecoder.a in LAME 3.99.5 and other products, allows remote attackers to c…

published 2017-06-25 9 y ago modified 2026-06-17 4 mo ago also EUVD-2017-18780

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

Summary

The III_i_stereo function in layer3.c in mpglib, as used in libmpgdecoder.a in LAME 3.99.5 and other products, allows remote attackers to cause a denial of service (buffer over-read and application crash) via a crafted audio file that is mishandled in the code for the "block_type == 2" case, a similar issue to CVE-2017-11126.

Patch / fix

  • lame Debian 14, Debian 13, Debian 12 3.99.5+repack1-8

debian advisories DEBIAN-CVE-2017-9870

  • lame Package Hub 12 SP2 3.100-6.1

opensuse advisories openSUSE-SU-2018:0543-1openSUSE-SU-2018:0544-1

  • lame Arch Linux 3.100-1

arch linux advisories AVG-330

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-9870 updated cvss 3.3

lame: buffer over-read in III_i_stereo function in layer3.c in mpglib

  • Red Hat Enterprise Linux 9 lame, lame-libs
    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.47% chance of exploitation in the next 30 days, higher than 73% of all scored CVEs (FIRST EPSS, 2026-11-09).

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.