Google Chrome up to 8.0.552.208 input validation

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

Summaryinfo

A vulnerability classified as problematic has been found in Google Chrome up to 8.0.552.208. This affects an unknown part. The manipulation leads to input validation. This vulnerability is traded as CVE-2011-0479. There is no exploit available. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability was found in Google Chrome up to 8.0.552.208 (Web Browser). It has been rated as problematic. This issue affects some unknown processing. The manipulation with an unknown input leads to a input validation vulnerability. Using CWE to declare the problem leads to CWE-20. The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly. Impacted is availability. The summary by CVE is:

Google Chrome before 8.0.552.237 and Chrome OS before 8.0.552.344 do not properly interact with extensions, which allows remote attackers to cause a denial of service via a crafted extension that triggers an uninitialized pointer.

The weakness was shared 01/12/2011 by Sergey Glazunov (SkyLined) with Chromium Development Community (Website). The advisory is shared at xforce.iss.net. The identification of this vulnerability is CVE-2011-0479. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available.

The vulnerability scanner Nessus provides a plugin with the ID 51511 (Google Chrome < 8.0.552.237 Multiple Vulnerabilities), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Windows. The commercial vulnerability scanner Qualys is able to test this issue with plugin 118908 (Google Chrome Prior to 8.0.552.237 Multiple Vulnerabilities).

Upgrading to version 8.0.552.209 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. Furthermore it is possible to detect and prevent this kind of attack with TippingPoint and the filter 11301.

The vulnerability is also documented in the databases at X-Force (64670), Tenable (51511), SecurityFocus (BID 45788†), OSVDB (70462†) and Vulnerability Center (SBV-29143†). The entries VDB-56075, VDB-56074, VDB-56073 and VDB-56072 are related to this item. 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: 5.3
VulDB Meta Temp Score: 5.1

VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Input validation
CWE: CWE-20
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: 51511
Nessus Name: Google Chrome < 8.0.552.237 Multiple Vulnerabilities
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍

OpenVAS ID: 801826
OpenVAS Name: Google Chrome multiple vulnerabilities - Jan11 (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 8.0.552.209
TippingPoint: 🔍
ISS Proventia IPS: 🔍
Fortigate IPS: 🔍

Timelineinfo

01/12/2011 🔍
01/12/2011 +0 days 🔍
01/12/2011 +0 days 🔍
01/12/2011 +0 days 🔍
01/14/2011 +1 days 🔍
01/14/2011 +0 days 🔍
01/17/2011 +3 days 🔍
01/18/2011 +1 days 🔍
03/19/2015 +1520 days 🔍
10/12/2021 +2399 days 🔍

Sourcesinfo

Vendor: google.com
Product: google.com

Advisory: xforce.iss.net
Researcher: Sergey Glazunov (SkyLined)
Organization: Chromium Development Community
Status: Not defined
Confirmation: 🔍

CVE: CVE-2011-0479 (🔍)
GCVE (CVE): GCVE-0-2011-0479
GCVE (VulDB): GCVE-100-56069

OVAL: 🔍

X-Force: 64670
SecurityFocus: 45788 - Google Chrome prior to 8.0.552.237 Multiple Security Vulnerabilities
Secunia: 42850
OSVDB: 70462 - Google Chrome Crafted Extension Interaction Uninitialized Pointer Remote DoS
Vulnerability Center: 29143 - Google Chrome and Chrome OS Remote DoS Vulnerability via a Crafted Extension, High

See also: 🔍

Entryinfo

Created: 03/19/2015 23:27
Updated: 10/12/2021 09:48
Changes: 03/19/2015 23:27 (70), 03/13/2017 09:57 (12), 10/11/2021 23:56 (5), 10/12/2021 00:09 (2), 10/12/2021 09:44 (1), 10/12/2021 09:48 (1)
Complete: 🔍
Cache ID: 216:F94: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 ▸

Do you know our Splunk app?

Download it now for free!