Google Chrome 19.0.1084.45 race condition

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

Summaryinfo

A vulnerability labeled as problematic has been found in Google Chrome 19.0.1084.45. Impacted is an unknown function. Executing a manipulation can lead to race condition. This vulnerability appears as CVE-2011-3090. In addition, an exploit is available. The affected component should be upgraded.

Detailsinfo

A vulnerability classified as critical was found in Google Chrome 19.0.1084.45 (Web Browser). This vulnerability affects an unknown part. The manipulation with an unknown input leads to a race condition vulnerability. The CWE definition for the vulnerability is CWE-362. The product contains a code sequence that can run concurrently with other code, and the code sequence requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence that is operating concurrently. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:

Race condition in Google Chrome before 19.0.1084.46 allows remote attackers to cause a denial of service or possibly have unspecified other impact via vectors related to worker processes.

The weakness was presented 05/15/2012 by Arthur Gerkis (psaldorn) with Chromium Development Community as 121223 as confirmed knowledge base article (Website). The advisory is shared for download at code.google.com. The public release was coordinated in cooperation with the vendor. This vulnerability was named CVE-2011-3090 since 08/09/2011. The exploitation appears to be difficult. 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.

It is declared as proof-of-concept. The vulnerability scanner Nessus provides a plugin with the ID 59103 (FreeBSD : chromium -- multiple vulnerabilities (1449af37-9eba-11e1-b9c1-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 165306 (SUSE Security Update for Update for Chromium, v8 (openSUSE-SU-2012:0656-1)).

Upgrading to version 19.0.1084.46 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 (59103), SecurityFocus (BID 53540†), OSVDB (81952†), Secunia (SA49194†) and SecurityTracker (ID 1027067†). See VDB-5400, VDB-5401, VDB-5402 and VDB-5403 for similar entries. Once again VulDB remains the best 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.1
VulDB Meta Temp Score: 7.3

VulDB Base Score: 8.1
VulDB Temp Score: 7.3
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Race condition
CWE: CWE-362
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: 59103
Nessus Name: FreeBSD : chromium -- multiple vulnerabilities (1449af37-9eba-11e1-b9c1-00262d5ed8ee)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 71375
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 19.0.1084.46

Timelineinfo

08/09/2011 🔍
05/15/2012 +280 days 🔍
05/15/2012 +0 days 🔍
05/15/2012 +0 days 🔍
05/15/2012 +0 days 🔍
05/16/2012 +1 days 🔍
05/16/2012 +0 days 🔍
05/16/2012 +0 days 🔍
05/18/2012 +2 days 🔍
05/25/2012 +7 days 🔍
03/24/2021 +3225 days 🔍

Sourcesinfo

Vendor: google.com
Product: google.com

Advisory: 121223
Researcher: Arthur Gerkis (psaldorn)
Organization: Chromium Development Community
Status: Confirmed
Confirmation: 🔍
Coordinated: 🔍

CVE: CVE-2011-3090 (🔍)
GCVE (CVE): GCVE-0-2011-3090
GCVE (VulDB): GCVE-100-5428

OVAL: 🔍

X-Force: 75595
SecurityFocus: 53540
Secunia: 49194 - Google Chrome Multiple Vulnerabilities, Highly Critical
OSVDB: 81952
SecurityTracker: 1027067

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

Entryinfo

Created: 05/25/2012 12:27
Updated: 03/24/2021 18:42
Changes: 05/25/2012 12:27 (81), 04/27/2018 09:18 (7), 03/24/2021 18:42 (3)
Complete: 🔍
Cache ID: 216:2B2:103

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!