Google Chrome 10.x memory corruption

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

Summaryinfo

A vulnerability classified as critical has been found in Google Chrome 10.x. This affects an unknown part. The manipulation leads to memory corruption. This vulnerability is referenced as CVE-2011-1291. Remote exploitation of the attack is possible. No exploit is available. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability was found in Google Chrome 10.x (Web Browser) and classified as critical. This issue affects some unknown processing. 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. The summary by CVE is:

Google Chrome before 10.0.648.204 does not properly handle base strings, which allows remote attackers to cause a denial of service or possibly have unspecified other impact via unknown vectors, related to a "buffer error."

The weakness was published 03/25/2011 by Sergey Glazunov (Slawomir Blazek) (Website). The advisory is shared at googlechromereleases.blogspot.com. The identification of this vulnerability is CVE-2011-1291 since 03/06/2011. 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 price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 03/19/2021). It is expected to see the exploit prices for this product increasing in the near future.

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

Upgrading 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 googlechromereleases.blogspot.com. The best possible mitigation is suggested to be upgrading to the latest version. A possible mitigation has been published even before and not after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at X-Force (66298), Tenable (52975), SecurityFocus (BID 47029†), Secunia (SA43859†) and Vulnerability Center (SBV-30693†). Similar entries are available at VDB-56943, VDB-56942, VDB-56941 and VDB-56940. 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: 7.3
VulDB Meta Temp Score: 7.0

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

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Memory corruption
CWE: CWE-119
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: 52975
Nessus Name: Google Chrome < 10.0.648.204 Multiple Vulnerabilities
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 68696
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: 🔍

0-Day Time: 🔍

Upgrade: chrome.google.com
Patch: googlechromereleases.blogspot.com

Timelineinfo

03/06/2011 🔍
03/24/2011 +18 days 🔍
03/24/2011 +0 days 🔍
03/24/2011 +0 days 🔍
03/25/2011 +1 days 🔍
03/25/2011 +0 days 🔍
03/25/2011 +0 days 🔍
03/28/2011 +3 days 🔍
04/18/2011 +21 days 🔍
03/19/2021 +3623 days 🔍

Sourcesinfo

Vendor: google.com
Product: google.com

Advisory: googlechromereleases.blogspot.com
Researcher: Sergey Glazunov (Slawomir Blazek)
Status: Not defined
Confirmation: 🔍

CVE: CVE-2011-1291 (🔍)
GCVE (CVE): GCVE-0-2011-1291
GCVE (VulDB): GCVE-100-4325

OVAL: 🔍

X-Force: 66298
SecurityFocus: 47029 - Google Chrome Prior to 10.0.648.204 Multiple Security Vulnerabilities
Secunia: 43859 - Google Chrome Multiple Vulnerabilities, Highly Critical
Vulnerability Center: 30693 - Google Chrome Prior to 10.0.648.204 Remote DoS Vulnerability due to a Buffer Error, Medium

See also: 🔍

Entryinfo

Created: 04/18/2011 02:00
Updated: 03/19/2021 08:27
Changes: 04/18/2011 02:00 (79), 04/17/2019 14:02 (10), 03/19/2021 08:22 (3), 03/19/2021 08:27 (1)
Complete: 🔍
Cache ID: 216:3A8: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 ▸

Want to know what is going to be exploited?

We predict KEV entries!