Google Chrome 24.0.1312.71 PPAPI Message Submenu Entries serialized_flash_menu.cc ReadMenu memory corruption
CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
9.0 | $0-$5k | 0.00 |
A vulnerability was found in Google Chrome 24.0.1312.71 (Web Browser). It has been rated as critical. Affected by this issue is the function ReadMenu
of the file ppapi/proxy/serialized_flash_menu.cc of the component PPAPI Message Submenu Entries Handler. 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. CVE summarizes:
Multiple unspecified vulnerabilities in the IPC layer in Google Chrome before 25.0.1364.97 on Windows and Linux, and before 25.0.1364.99 on Mac OS X, allow remote attackers to cause a denial of service or possibly have other impact via unknown vectors.
The weakness was released 02/21/2013 by Chris Evans (Alexander) with Google Chrome Security Team as Issue 168710 as confirmed bug report (Website). The advisory is available at code.google.com. This vulnerability is handled as CVE-2013-0892 since 01/07/2013. The exploitation is known to be difficult. The attack may be launched remotely. No form of authentication is required for exploitation. Technical details as well as a exploit are known. The structure of the vulnerability defines a possible price range of USD $0-$5k at the moment (estimation calculated on 11/25/2018). It is expected to see the exploit prices for this product increasing in the near future.The following code is the reason for this vulnerability:
PP_Flash_Menu* ReadMenu(...) if (!m->ReadUInt32(iter, &menu->count)) { ... } ... menu->items = new PP_Flash_MenuItem[menu->count];The advisory points out:
Note that 64-bit will be fine here, but 32-bit (e.g. Lucas devices) will not.
It is declared as proof-of-concept. The vulnerability scanner Nessus provides a plugin with the ID 64859 (FreeBSD : chromium -- multiple vulnerabilities (dfd92cb2-7d48-11e2-ad48-00262d5ed8ee)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family FreeBSD Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 165877 (SUSE Security Update for Chromium: Updated to 27.0.1425 (openSUSE-SU-2013:0454-1)).
Upgrading to version 25.0.1364.97 eliminates this vulnerability. The upgrade is hosted for download at chrome.google.com. Applying a patch is able to eliminate this problem. The bugfix is ready for download at src.chromium.org. The best possible mitigation is suggested to be upgrading to the latest version. A possible mitigation has been published immediately after the disclosure of the vulnerability. The vulnerability will be addressed with the following lines of code:
const uint32_t kMaxMenuEntries = 1000; (…) if (menu->count > kMaxMenuEntries) { FreeMenu(menu); return NULL; }
The vulnerability is also documented in the databases at X-Force (82288) and Tenable (64859). googlechromereleases.blogspot.com is providing further details. Entries connected to this vulnerability are available at 7789, 7790, 7791 and 7792.
Product
Type
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB CVSS-B Score: 🔍VulDB CVSS-BT Score: 🔍
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 10.0VulDB Meta Temp Score: 9.0
VulDB Base Score: 10.0
VulDB Temp Score: 9.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
AV | AC | Au | C | I | A |
---|---|---|---|---|---|
💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
---|---|---|---|---|---|
unlock | unlock | unlock | unlock | unlock | unlock |
unlock | unlock | unlock | unlock | unlock | unlock |
unlock | unlock | unlock | unlock | unlock | unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Memory corruptionCWE: CWE-119
ATT&CK: Unknown
Local: No
Remote: Yes
Availability: 🔍
Status: Proof-of-Concept
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
0-Day | unlock | unlock | unlock | unlock |
---|---|---|---|---|
Today | unlock | unlock | unlock | unlock |
Nessus ID: 64859
Nessus Name: FreeBSD : chromium -- multiple vulnerabilities (dfd92cb2-7d48-11e2-ad48-00262d5ed8ee)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍
OpenVAS ID: 803314
OpenVAS Name: Google Chrome Multiple Vulnerabilities-01 March 2013 (Linux)
OpenVAS File: 🔍
OpenVAS Family: 🔍
Qualys ID: 🔍
Qualys Name: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Upgrade: Chrome 25.0.1364.97
Patch: src.chromium.org
Timeline
01/07/2013 🔍02/21/2013 🔍
02/21/2013 🔍
02/21/2013 🔍
02/21/2013 🔍
02/22/2013 🔍
02/23/2013 🔍
02/24/2013 🔍
03/05/2013 🔍
12/20/2013 🔍
11/25/2018 🔍
Sources
Vendor: google.comProduct: google.com
Advisory: Issue 168710
Researcher: Chris Evans (Alexander)
Organization: Google Chrome Security Team
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2013-0892 (🔍)
OVAL: 🔍
X-Force: 82288
Vulnerability Center: 38625 - Google Chrome Before 25.0.1364.97 Multiple Unspecified Remote Vulnerabilities in IPC Layer, Medium
SecurityFocus: 58101 - RETIRED: Google Chrome Multiple Security Vulnerabilities
Secunia: 52320 - Google Chrome Multiple Vulnerabilities, Highly Critical
OSVDB: 101168
scip Labs: https://www.scip.ch/en/?labs.20161013
Misc.: 🔍
See also: 🔍
Entry
Created: 12/20/2013 09:30Updated: 11/25/2018 10:02
Changes: 12/20/2013 09:30 (97), 11/25/2018 10:02 (4)
Complete: 🔍
No comments yet. Languages: en.
Please log in to comment.