Google Chrome up to 18.0.1025.162 Sandbox IPC resource management

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.5$0-$5k0.00

Summaryinfo

A vulnerability was found in Google Chrome up to 18.0.1025.162 and classified as problematic. This vulnerability affects unknown code of the component Sandbox IPC. Executing a manipulation can lead to resource management. This vulnerability appears as CVE-2011-3079. The attack may be performed from remote. In addition, an exploit is available. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability classified as critical was found in Google Chrome up to 18.0.1025.162 (Web Browser). This vulnerability affects an unknown code of the component Sandbox IPC. The manipulation with an unknown input leads to a resource management vulnerability. The CWE definition for the vulnerability is CWE-399. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:

The Inter-process Communication (IPC) implementation in Google Chrome before 18.0.1025.168, as used in Mozilla Firefox before 38.0 and other products, does not properly validate messages, which has unspecified impact and attack vectors.

The bug was discovered 04/30/2012. The weakness was presented 04/30/2012 by Willem Pinckaers (PinkiePie aka PwniePie) as 117627 as confirmed knowledge base article (Website). The advisory is available at code.google.com. The public release was coordinated in cooperation with the vendor. This vulnerability was named CVE-2011-3079 since 08/09/2011. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. Technical details are unknown but a private exploit is available.

The vulnerability scanner Nessus provides a plugin with the ID 83800 (openSUSE Security Update : MozillaThunderbird (openSUSE-2015-374)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family SuSE Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 167834 (OpenSuSE Security Update for MozillaThunderbird (openSUSE-SU-2015:0935-1)).

Upgrading to version 18.0.1025.168 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 (83800), SecurityFocus (BID 53309†), OSVDB (81645†), Secunia (SA48992†) and SecurityTracker (ID 1027001†). See VDB-5332, VDB-5333, VDB-5334 and VDB-5337 for similar entries. If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 9.8
VulDB Meta Temp Score: 8.5

VulDB Base Score: 9.8
VulDB Temp Score: 8.5
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Resource management
CWE: CWE-399 / CWE-404
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Access: Private
Status: Proof-of-Concept

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 83800
Nessus Name: openSUSE Security Update : MozillaThunderbird (openSUSE-2015-374)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍
Nessus Port: 🔍

OpenVAS ID: 71386
OpenVAS Name: FreeBSD Ports: chromium
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 18.0.1025.168

Timelineinfo

08/09/2011 🔍
04/30/2012 +265 days 🔍
04/30/2012 +0 days 🔍
04/30/2012 +0 days 🔍
04/30/2012 +0 days 🔍
05/01/2012 +1 days 🔍
05/01/2012 +0 days 🔍
05/02/2012 +1 days 🔍
05/05/2012 +3 days 🔍
05/07/2012 +2 days 🔍
05/26/2015 +1114 days 🔍
11/25/2025 +3836 days 🔍

Sourcesinfo

Vendor: google.com
Product: google.com

Advisory: 117627
Researcher: Willem Pinckaers (PinkiePie aka PwniePie)
Status: Confirmed
Confirmation: 🔍
Coordinated: 🔍

CVE: CVE-2011-3079 (🔍)
GCVE (CVE): GCVE-0-2011-3079
GCVE (VulDB): GCVE-100-5338

OVAL: 🔍

X-Force: 75271
SecurityFocus: 53309 - Google Chrome Prior to 18.0.1025.168 Multiple Security Vulnerabilities
Secunia: 48992 - Google Chrome Multiple Vulnerabilities, Highly Critical
OSVDB: 81645
SecurityTracker: 1027001

scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍

Entryinfo

Created: 05/07/2012 12:52
Updated: 11/25/2025 19:00
Changes: 05/07/2012 12:52 (90), 05/02/2019 07:07 (1), 03/24/2021 10:52 (3), 11/25/2025 19:00 (17)
Complete: 🔍
Cache ID: 216:7AB:103

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you need the next level of professionalism?

Upgrade your account now!