Google Chrome up to 4.1.249.1055 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.
9.5$5k-$25k0.00

Summaryinfo

A vulnerability was found in Google Chrome up to 4.1.249.1055. It has been classified as critical. The impacted element is an unknown function. Performing a manipulation results in memory corruption. This vulnerability is identified as CVE-2010-2901. There is not any exploit available. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability classified as very critical has been found in Google Chrome up to 4.1.249.1055 (Web Browser). This affects an unknown code block. 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:

The rendering implementation in Google Chrome before 5.0.375.125 allows remote attackers to cause a denial of service (memory corruption) or possibly have unspecified other impact via unknown vectors.

The weakness was released 07/28/2010 by Jose A. Vazquez (Inferno) with Google Chrome Security Team (Website). It is possible to read the advisory at secunia.com. This vulnerability is uniquely identified as CVE-2010-2901. The exploitability is told to be easy. 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 $5k-$25k at the moment (estimation calculated on 09/21/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 51950 (FreeBSD : webkit-gtk2 -- Multiple vurnabilities. (35ecdcbe-3501-11e0-afcd-0015f2db7bde)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family FreeBSD Local Security Checks. 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 to version 4.1.249.1056 eliminates this vulnerability. The upgrade is hosted for download at chrome.google.com.

The vulnerability is also documented in the databases at Tenable (51950), SecurityFocus (BID 41976†) and Vulnerability Center (SBV-26611†). Entries connected to this vulnerability are available at VDB-4155, VDB-4190, VDB-54832 and VDB-54173. 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: 10.0
VulDB Meta Temp Score: 9.5

VulDB Base Score: 10.0
VulDB Temp Score: 9.5
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: 51950
Nessus Name: FreeBSD : webkit-gtk2 -- Multiple vurnabilities. (35ecdcbe-3501-11e0-afcd-0015f2db7bde)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Port: 🔍

OpenVAS ID: 69325
OpenVAS Name: Debian Security Advisory DSA 2188-1 (webkit)
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 4.1.249.1056

Timelineinfo

07/26/2010 🔍
07/28/2010 +1 days 🔍
07/28/2010 +0 days 🔍
07/28/2010 +0 days 🔍
07/28/2010 +0 days 🔍
08/01/2010 +4 days 🔍
02/11/2011 +194 days 🔍
03/19/2015 +1497 days 🔍
09/21/2021 +2378 days 🔍

Sourcesinfo

Vendor: google.com
Product: google.com

Advisory: dsa-2188⛔
Researcher: Jose A. Vazquez (Inferno)
Organization: Google Chrome Security Team
Status: Not defined
Confirmation: 🔍

CVE: CVE-2010-2901 (🔍)
GCVE (CVE): GCVE-0-2010-2901
GCVE (VulDB): GCVE-100-54171

OVAL: 🔍

SecurityFocus: 41976 - Google Chrome prior to 5.0.375.125 Multiple Security Vulnerabilities
Secunia: 40743
Vulnerability Center: 26611 - Google Chrome <5.0.375.125 Rendering Implementation Remote Memory Corruption Vulnerability, Medium

See also: 🔍

Entryinfo

Created: 03/19/2015 14:37
Updated: 09/21/2021 08:54
Changes: 03/19/2015 14:37 (65), 03/01/2017 10:15 (11), 09/21/2021 08:50 (6), 09/21/2021 08:54 (1)
Complete: 🔍
Cache ID: 216::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 ▸

Want to know what is going to be exploited?

We predict KEV entries!