CVE-2017-7865 json
FFmpeg before 2017-01-24 has an out-of-bounds write caused by a heap-based buffer overflow related to the ipvideo_decode_block_opcode_0xA f…
published 2017-04-14 9 y ago modified 2026-06-17 4 mo ago also EUVD-2017-16840
- cvss
- 9.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.6%
- EPSS 2.6% chance of exploitation in 30 days, percentile 85%
- public exploits
- 0
- none known
Summary
FFmpeg before 2017-01-24 has an out-of-bounds write caused by a heap-based buffer overflow related to the ipvideo_decode_block_opcode_0xA function in libavcodec/interplayvideo.c and the avcodec_align_dimensions2 function in libavcodec/utils.c.
Patch / fix
- ffmpeg Debian 14, Debian 13, Debian 12 7:3.2.4-1
debian advisories DEBIAN-CVE-2017-7865
- ffmpeg Ubuntu 16.04 LTS 7:2.8.11-0ubuntu0.16.04.1
ubuntu advisories UBUNTU-CVE-2017-7865
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- ffmpeg2 Package Hub 12 SP1 2.8.11-12.1
opensuse advisories openSUSE-SU-2017:1532-1
Exploit prediction
2.56% chance of exploitation in the next 30 days, higher than 85% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 9.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-787 Out-of-bounds Write
References
-
github.com
/FFmpeg/FFmpeg/commit/2080bc33717955a0e4268e738acf8c1eeddbf8cb
patch, third-party-advisory
-
lists.debian.org
/debian-lts-announce/2019/02/msg00005.html
mailing-list, third-party-advisory
-
bugs.chromium.org
/p/oss-fuzz/issues/detail?id=452
third-party-advisory, vdb-entry
-
securityfocus.com
/bid/97685
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2017-7865
- NVD CVE-2017-7865
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.