Google Chrome up to 54 FFmpeg memory corruption

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
8.6$5k-$25k0.00

Summaryinfo

A vulnerability classified as critical has been found in Google Chrome up to 54. This impacts an unknown function of the component FFmpeg. The manipulation leads to memory corruption. This vulnerability is referenced as CVE-2016-5199. Remote exploitation of the attack is possible. No exploit is available. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as critical, has been found in Google Chrome up to 54 (Web Browser). This issue affects some unknown processing of the component FFmpeg. The manipulation with an unknown input leads to a memory corruption vulnerability. Using CWE to declare the problem leads to CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. Impacted is confidentiality, integrity, and availability.

The bug was discovered 11/09/2016. The weakness was published 11/09/2016 by Paul Mehta with Google as Stable Channel Update for Desktop, November 2016 as confirmed release notes (Blog). It is possible to read the advisory at googlechromereleases.blogspot.com. The public release has been coordinated with Google. The identification of this vulnerability is CVE-2016-5199 since 05/31/2016. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. It demands that the victim is doing some kind of user interaction. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 05/14/2026). It is expected to see the exploit prices for this product increasing in the near future.

The vulnerability scanner Nessus provides a plugin with the ID 94677 (Google Chrome < 54.0.2840.98 Multiple Vulnerabilities (macOS)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family MacOS X Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 196644 (Ubuntu Security Notification for Oxide-qt Vulnerabilities (USN-3133-1)).

Upgrading to version 54.0.2840.98, 54.0.2840.99 or 54.0.2840.100 eliminates this vulnerability. The upgrade is hosted for download at chrome.google.com. A possible mitigation has been published immediately after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at Tenable (94677), SecurityFocus (BID 94196†) and SecurityTracker (ID 1037273†). Similar entries are available at VDB-93576, VDB-93577 and VDB-93578. Be aware that VulDB is the high quality source for vulnerability data.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 8.8
VulDB Meta Temp Score: 8.6

VulDB Base Score: 8.8
VulDB Temp Score: 8.4
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 8.8
NVD Vector: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Memory corruption
CWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 94677
Nessus Name: Google Chrome < 54.0.2840.98 Multiple Vulnerabilities (macOS)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 855379
OpenVAS Name: Google Chrome Security Updates(stable-channel-update-for-desktop_9-2016-11)-Linux
OpenVAS File: 🔍
OpenVAS Family: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍

Upgrade: Chrome 54.0.2840.98/54.0.2840.99/54.0.2840.100

Timelineinfo

05/31/2016 🔍
11/09/2016 +162 days 🔍
11/09/2016 +0 days 🔍
11/09/2016 +0 days 🔍
11/09/2016 +0 days 🔍
11/10/2016 +1 days 🔍
11/11/2016 +1 days 🔍
11/11/2016 +0 days 🔍
01/19/2017 +69 days 🔍
05/14/2026 +3401 days 🔍

Sourcesinfo

Vendor: google.com
Product: google.com

Advisory: Stable Channel Update for Desktop, November 2016
Researcher: Paul Mehta
Organization: Google
Status: Confirmed
Confirmation: 🔍
Coordinated: 🔍

CVE: CVE-2016-5199 (🔍)
GCVE (CVE): GCVE-0-2016-5199
GCVE (VulDB): GCVE-100-93575

OVAL: 🔍

SecurityFocus: 94196 - Google Chrome Multiple Security Vulnerabilities
SecurityTracker: 1037273

See also: 🔍

Entryinfo

Created: 11/11/2016 16:26
Updated: 05/14/2026 00:50
Changes: 11/11/2016 16:26 (77), 05/30/2019 09:53 (14), 10/03/2022 08:56 (3), 05/14/2026 00:50 (15)
Complete: 🔍
Cache ID: 216::103

Be aware that VulDB is the high quality source for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you need the next level of professionalism?

Upgrade your account now!