CVE-2019-9718: Medium severity FFmpeg FFmpeg vulnerability
In FFmpeg 3.2 and 4.1, a denial of service in the subtitle decoder allows attackers to hog the CPU via a crafted video file in Matroska format, because ffhtmlmarkuptoass in libavcodec/htmlsubtitles.c has a complex format argument to sscanf.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/ffmpegto a version that resolves this vulnerability.Fixed in 7:4.3.7-0+deb11u1Fixed in 7:4.3.9-0+deb11u2Fixed in 7:5.1.8-0+deb12u1Fixed in 7:7.1.3-0+deb13u1Fixed in 7:8.0.1-3Fixed in 7:8.1-3 - Upgrade
Upgrade
alpine/ffmpegto a version that resolves this vulnerability.Fixed in 4.1.3-r0 - Upgrade
Upgrade
alpine/ffmpegto a version that resolves this vulnerability.Fixed in 3.4.6-r0 - Upgrade
Upgrade
alpine/ffmpegto a version that resolves this vulnerability.Fixed in 4.0.4-r0 - Upgrade
Upgrade
alpine/ffmpeg4to a version that resolves this vulnerability.Fixed in 4.1.3-r0
Event History
Frequently Asked Questions
What is the vulnerability ID for the FFmpeg vulnerability?
The vulnerability ID for the FFmpeg vulnerability is CVE-2019-9718.
What is the severity of CVE-2019-9718?
The severity of CVE-2019-9718 is medium (CVSS score: 6.5).
How does the vulnerability in FFmpeg 3.2 and 4.1 affect the CPU?
The vulnerability in FFmpeg 3.2 and 4.1 allows attackers to hog the CPU via a crafted video file in Matroska format.
Which versions of FFmpeg are affected by CVE-2019-9718?
FFmpeg versions 3.2 and 4.1 are affected by CVE-2019-9718.
Where can I find more information about CVE-2019-9718?
You can find more information about CVE-2019-9718 at the following references: [1](http://www.securityfocus.com/bid/107382), [2](https://git.ffmpeg.org/gitweb/ffmpeg.git/commit/1f00c97bc3475c477f3c468cf2d924d5761d0982), [3](https://github.com/FFmpeg/FFmpeg/commit/23ccf3cabb4baf6e8af4b1af3fcc59c904736f21).