Google Chrome 5.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 marked as critical has been reported in Google Chrome 5.x. This affects an unknown function. Performing a manipulation results in memory corruption. This vulnerability is known as CVE-2010-2897. Remote exploitation of the attack is possible. No exploit is available. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability was found in Google Chrome 5.x (Web Browser). It has been classified as critical. This affects an unknown code. The manipulation with an unknown input leads to a memory corruption vulnerability. CWE is classifying the issue as 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. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

Google Chrome before 5.0.375.125 does not properly mitigate an unspecified flaw in the Windows kernel, which has unknown impact and attack vectors.

The weakness was published 07/27/2010 by Aki Helin (Inferno) with Google (Website). It is possible to read the advisory at googlechromereleases.blogspot.com. This vulnerability is uniquely identified as CVE-2010-2897 since 07/28/2010. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 03/18/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 47859 (Google Chrome < 5.0.375.125 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 118311 (Google Chrome prior to 5.0.375.125 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 before and not just after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at Tenable (47859), SecurityFocus (BID 41976†), OSVDB (66752†) and Secunia (SA40743†). Similar entries are available at VDB-4190, VDB-54832, VDB-54173 and VDB-54172. Statistical analysis made it clear that VulDB provides the best quality 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: 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: 47859
Nessus Name: Google Chrome < 5.0.375.125 Multiple Vulnerabilities
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 902092
OpenVAS Name: Google Chrome Multiple Unspecified Vulnerabilities - July 10
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

07/26/2010 🔍
07/26/2010 +0 days 🔍
07/27/2010 +1 days 🔍
07/27/2010 +0 days 🔍
07/27/2010 +0 days 🔍
07/28/2010 +0 days 🔍
07/28/2010 +0 days 🔍
08/19/2010 +22 days 🔍
03/18/2021 +3864 days 🔍

Sourcesinfo

Vendor: google.com
Product: google.com

Advisory: googlechromereleases.blogspot.com
Researcher: Aki Helin (Inferno)
Organization: Google
Status: Not defined
Confirmation: 🔍

CVE: CVE-2010-2897 (🔍)
GCVE (CVE): GCVE-0-2010-2897
GCVE (VulDB): GCVE-100-4155

OVAL: 🔍

SecurityFocus: 41976 - Google Chrome prior to 5.0.375.125 Multiple Security Vulnerabilities
Secunia: 40743 - Google Chrome Multiple Vulnerabilities, Highly Critical
OSVDB: 66752 - Google Chrome Windows Kernel Flaw Mitigation Weakness Unspecified Issue

See also: 🔍

Entryinfo

Created: 08/19/2010 02:00
Updated: 03/18/2021 08:32
Changes: 08/19/2010 02:00 (74), 04/17/2019 14:02 (7), 03/18/2021 08:29 (7), 03/18/2021 08:32 (1)
Complete: 🔍
Cache ID: 216:878:103

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Might our Artificial Intelligence support you?

Check our Alexa App!