CVE-2017-8419 Memory corruption in n/a

High 7.8 Published Updated

Remote attackers can cause denial of service or potential code execution via crafted WAV or AIFF files due to integer handling errors in the LAME library.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Local or same network only
Victim action needed
A user has to click or open something
Fix
Available

What is CVE-2017-8419?

CVE-2017-8419 is a high-severity memory corruption vulnerability in n/a, published on 2 May 2017. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

Official description

LAME through 3.99.5 relies on the signed integer data type for values in a WAV or AIFF header, which allows remote attackers to cause a denial of service (stack-based buffer overflow or heap-based buffer overflow) or possibly have unspecified other impact via a crafted file, as demonstrated by mishandling of num_channels.

Weakness: CWE-119

Which versions are affected by CVE-2017-8419?

It affects 1 product.

Products include Lame Project Lame.

How do I fix CVE-2017-8419?

Upgrade to a fixed version.

Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.

Is CVE-2017-8419 being exploited?

There is no known exploitation of CVE-2017-8419 in the wild and no public exploit code.

Sources

Also known as DEBIAN-CVE-2017-8419, GHSA-fg7v-43m7-5p33, UBUNTU-CVE-2017-8419.

Is CVE-2017-8419 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free