CVE-2017-11720: There is a division-by-zero vulnerability in LAME 3.99.5, caused by a malformed input file.

This week

CRITICAL 9.8REMOTEDOWNGRADE

CVE-2017-11720 is a critical-severity flaw (CVSS 9.8) affecting lame. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

There is a division-by-zero vulnerability in LAME 3.99.5, caused by a malformed input file.

Why this priority

Critical 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	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	2.5% (top 15%)
CISA exploited list	No
Weakness	CWE-369
Published	2017-07-28
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: lame project

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

Am I affected?

Timeline

2017-07-28 14:29 UTCPublished CVE record published
2026-06-17 01:02 UTCUpdated Record last modified

lame project lame DOWNGRADE

Affected: 3.99.5

Fixed in: no fixed release known

Safe to downgrade to: a release before 3.99.5

1. Check installed version

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

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

apt-cache madison lame sudo apt install lame=<VERSION_BEFORE_3.99.5> sudo apt-mark hold lame

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

dnf --showduplicates list lame sudo dnf downgrade lame-<VERSION_BEFORE_3.99.5> sudo dnf versionlock add lame

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-11720?

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

Is CVE-2017-11720 being exploited?

CVE-2017-11720 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-11720 affect?

CVE-2017-11720 affects lame. Severity is critical (CVSS 9.8). There is a division-by-zero vulnerability in LAME 3.99.5, caused by a malformed input file.

How urgent is CVE-2017-11720?

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

Related CVEs

CVE-2017-9872 HIGH 7.8 DOWNGRADE The III_dequantize_sample function in layer3.c in mpglib, as used in libmpgdecoder.a in LAME 3.99.5 and other
CVE-2017-9871 HIGH 7.8 DOWNGRADE The III_i_stereo function in layer3.c in mpglib, as used in libmpgdecoder.a in LAME 3.99.5 and other products,
CVE-2017-9870 MEDIUM 5.5 DOWNGRADE The III_i_stereo function in layer3.c in mpglib, as used in libmpgdecoder.a in LAME 3.99.5 and other products,
CVE-2017-9869 MEDIUM 5.5 DOWNGRADE The II_step_one function in layer2.c in mpglib, as used in libmpgdecoder.a in LAME 3.99.5 and other products,
CVE-2017-9412 MEDIUM 5.5 DOWNGRADE The unpack_read_samples function in frontend/get_audio.c in LAME 3.99.5 allows remote attackers to cause a den

References

← Back to latest CVEs