CVE-2018-6621 json
The decode_frame function in libavcodec/utvideodec.c in FFmpeg through 3.2 allows remote attackers to cause a denial of service (out of arr…
published 8y ago modified 4mo ago also EUVD-2018-18368
- cvss
- 6.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.2%
- EPSS 2.2% chance of exploitation in 30 days, percentile 82%
- public exploits
- 0
- none known
Summary
The decode_frame function in libavcodec/utvideodec.c in FFmpeg through 3.2 allows remote attackers to cause a denial of service (out of array read) via a crafted AVI file.
Patch / fix
- ffmpeg Debian 14, Debian 13, Debian 12 7:3.4.2-1
debian advisories DEBIAN-CVE-2018-6621
- ffmpeg-4 openSUSE Tumbleweed 4.4-5.2
- ffmpeg Package Hub 12 SP2 3.4.2-14.1
opensuse advisories openSUSE-SU-2024:10754-1openSUSE-SU-2018:0470-1openSUSE-SU-2018:0476-1
Is CVE-2018-6621 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
2.16% chance of exploitation in the next 30 days, higher than 82% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 6.5 | CVSS:3.1/AV:N/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
-
- CWE-125 Out-of-bounds Read
References
-
git.ffmpeg.org
/gitweb/ffmpeg.git/commit/118e1b0b3370dd1c0da442901b486689efd1654b
patch, third-party-advisory
-
github.com
/FFmpeg/FFmpeg/commit/22aa37c0fedf14531783189a197542a055959b6c
patch, third-party-advisory
-
debian.org
/security/2018/dsa-4249
vendor-advisory, third-party-advisory
-
securityfocus.com
/bid/102950
vdb-entry, third-party-advisory
-
lists.debian.org
/debian-lts-announce/2019/01/msg00006.html
mailing-list, third-party-advisory
Sources
- CVE List CVE-2018-6621
- NVD CVE-2018-6621
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.