CVE-2017-1000460 json
In line libavcodec/h264dec.c:500 in libav(v13_dev0), ffmpeg(n3.4), chromium(56 prior Feb 13, 2017), the return value of init_get_bits is ig…
published 8y ago modified 4mo ago also EUVD-2017-1587
- cvss
- 6.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 42%
- public exploits
- 0
- none known
Summary
In line libavcodec/h264dec.c:500 in libav(v13_dev0), ffmpeg(n3.4), chromium(56 prior Feb 13, 2017), the return value of init_get_bits is ignored and get_ue_golomb(&gb) is called on an uninitialized get_bits context, which causes a NULL deref exception.
Patch / fix
- ffmpeg Debian 14, Debian 13, Debian 12 7:3.1.1-1
debian advisories DEBIAN-CVE-2017-1000460
Is CVE-2017-1000460 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
0.49% chance of exploitation in the next 30 days, higher than 42% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- bugzilla.libav.org https://bugzilla.libav.org/show_bug.cgi?id=952 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 6.5 | CVSS:3.0/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-476 NULL Pointer Dereference
- Technology feeds
References
-
chromium.googlesource.com
/chromium/third_party/ffmpeg/+/8e313ca08800178efce00045e07dc494d437b70c
issue-tracking, patch
-
lists.ffmpeg.org
/pipermail/ffmpeg-cvslog/2017-January/104221.html
issue-tracking, patch
-
bugzilla.libav.org
/show_bug.cgi?id=952
exploit, issue-tracking, third-party-advisory
-
lists.debian.org
/debian-lts-announce/2019/03/msg00041.html
mailing-list
Sources
- CVE List CVE-2017-1000460
- NVD CVE-2017-1000460
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.