VDB

CVE-2017-5024

CVE-2017-5024 PUBLISHED

Reported by chrome · Published February 17, 2017

FFmpeg in Google Chrome prior to 56.0.2924.76 for Linux, Windows and Mac, failed to perform proper bounds checking, which allowed a remote attacker to potentially exploit heap corruption via a crafted video file.

Fixed versions

Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.

PackageEcosystemFixed in
chromegoogle55.0.2883.87
ffmpegUbuntu:16.04:LTS7:2.8.11-0ubuntu0.16.04.1
chromium-browserUbuntu:14.04:LTS58.0.3029.81-0ubuntu0.14.04.1172

Affected products

VendorProductVersions
n/aGoogle Chrome prior to 56.0.2924.76 for Linux, Windows and MacGoogle Chrome prior to 56.0.2924.76 for Linux, Windows and Mac
n/aGoogle Chrome prior to 56.0.2924.76 for Linux, Windows and MacGoogle Chrome prior to 56.0.2924.76 for Linux, Windows and Mac
archffmpeg0
archchromium0
alpineffmpeg0, 0, 0

Timeline

  • Jan 26, 2017 CVE Published
  • Apr 14, 2021 EPSS Score (30 in total, the first dated here)
  • Mar 6, 2026 Distribution Patch (2 in total, the first dated here)
  • Mar 6, 2026 Security Advisory (6 in total, the first dated here)
  • Sep 20, 2026 CVE Updated
  • Sep 29, 2026 Coalition ESS Score

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2017-5024
vulnetix vdb fixes CVE-2017-5024

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2017-5024/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

References

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›