Google Chrome 22.0.1229.92 Inter-Process Communication access control

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

Summaryinfo

A vulnerability was found in Google Chrome 22.0.1229.92. It has been rated as critical. This affects an unknown function of the component Inter-Process Communication. This manipulation causes access control. This vulnerability is registered as CVE-2012-5376. Furthermore, an exploit is available. Upgrading the affected component is advised.

Detailsinfo

A vulnerability was found in Google Chrome 22.0.1229.92 (Web Browser). It has been declared as critical. Affected by this vulnerability is an unknown function of the component Inter-Process Communication. The manipulation with an unknown input leads to a access control vulnerability. The CWE definition for the vulnerability is CWE-264. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

the inter-process communication (ipc) implementation in google chrome before 22.0.1229.94 allows remote attackers to bypass intended sandbox restrictions and write to arbitrary files by leveraging access to a renderer process a different vulnerability than cve-2012-5112.

The weakness was published 10/10/2012 by PwniePie as confirmed blog post (Website). The advisory is shared at blog.chromium.org. The public release has been coordinated with Google. This vulnerability is known as CVE-2012-5376 since 10/11/2012. The exploitation appears to be difficult. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are unknown but a private exploit is available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 04/18/2021). It is expected to see the exploit prices for this product increasing in the near future.MITRE ATT&CK project uses the attack technique T1068 for this issue.

It is declared as proof-of-concept. The vulnerability scanner Nessus provides a plugin with the ID 62652 (GLSA-201210-07 : Chromium: Multiple vulnerabilities), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Gentoo Local Security Checks.

Upgrading to version 22.0.1229.94 eliminates this vulnerability. The upgrade is hosted for download at googlechromereleases.blogspot.com.

The vulnerability is also documented in the databases at X-Force (79186), Tenable (62652), SecurityFocus (BID 55867†), OSVDB (86156†) and Secunia (SA50954†). Additional details are provided at code.google.com. Similar entries are available at VDB-5897, VDB-6682, VDB-6684 and VDB-8774. If you want to get the best quality for vulnerability data then you always have to consider 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: 9.1

VulDB Base Score: 10.0
VulDB Temp Score: 8.7
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 9.6
NVD Vector: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Access control
CWE: CWE-264
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: 62652
Nessus Name: GLSA-201210-07 : Chromium: Multiple vulnerabilities
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍

OpenVAS ID: 802474
OpenVAS Name: Google Chrome Multiple Vulnerabilities-02 Oct12 (Linux)
OpenVAS File: 🔍
OpenVAS Family: 🔍

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: Chrome 22.0.1229.94

Timelineinfo

10/10/2012 🔍
10/10/2012 +0 days 🔍
10/10/2012 +0 days 🔍
10/11/2012 +1 days 🔍
10/11/2012 +0 days 🔍
10/12/2012 +1 days 🔍
10/16/2012 +4 days 🔍
11/08/2012 +23 days 🔍
04/18/2021 +3083 days 🔍

Sourcesinfo

Vendor: google.com
Product: google.com

Advisory: blog.chromium.org
Researcher: PwniePie
Status: Confirmed
Confirmation: 🔍
Coordinated: 🔍

CVE: CVE-2012-5376 (🔍)
GCVE (CVE): GCVE-0-2012-5376
GCVE (VulDB): GCVE-100-6685

OVAL: 🔍

X-Force: 79186 - Google Chrome IPC security bypass, Medium Risk
SecurityFocus: 55867 - Google Chrome Prior to 22.0.1229.94 Multiple Security Vulnerabilities
Secunia: 50954 - Google Chrome Two Vulnerabilities, Highly Critical
OSVDB: 86156
Vulnerability Center: 37069 - The IPC Implementation in Google Chrome Before 22.0.1229.94 Remote Security Bypass Vulnerability, Medium

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

Entryinfo

Created: 10/16/2012 11:20
Updated: 04/18/2021 10:54
Changes: 10/16/2012 11:20 (52), 04/20/2017 14:21 (35), 04/18/2021 10:47 (13), 04/18/2021 10:54 (1)
Complete: 🔍
Committer:
Cache ID: 216:485:103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Might our Artificial Intelligence support you?

Check our Alexa App!