Google Chrome WebKit Timer.cpp exceptional 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.
6.3$5k-$25k0.00

Summaryinfo

A vulnerability, which was classified as critical, was found in Google Chrome. The impacted element is an unknown function of the file Timer.cpp of the component WebKit. Such manipulation leads to exceptional condition. This vulnerability is documented as CVE-2011-2807. The attack can be executed remotely. There is not any exploit available. You should upgrade the affected component.

Detailsinfo

A vulnerability was found in Google Chrome (Web Browser) (affected version not known). It has been rated as critical. Affected by this issue is some unknown functionality of the file Timer.cpp of the component WebKit. The manipulation with an unknown input leads to a exceptional condition vulnerability. Using CWE to declare the problem leads to CWE-755. The product does not handle or incorrectly handles an exceptional condition. Impacted is availability. CVE summarizes:

Incorrect handling of timer information in Timer.cpp in WebKit in Google Chrome before Blink M13.

The weakness was released 11/07/2019. This vulnerability is handled as CVE-2011-2807 since 07/20/2011. The attack may be launched remotely. No form of authentication is required for exploitation. Successful exploitation requires user interaction by the victim. There are known technical details, but no exploit is available. The current price for an exploit might be approx. USD $5k-$25k (estimation calculated on 02/05/2024). It is expected to see the exploit prices for this product increasing in the near future.

Upgrading eliminates this vulnerability.

Entries connected to this vulnerability are available at VDB-145195, VDB-145194 and VDB-145193. Once again VulDB remains the best source for vulnerability data.

Productinfo

Type

Vendor

Name

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.5
VulDB Meta Temp Score: 6.3

VulDB Base Score: 6.5
VulDB Temp Score: 6.2
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 6.5
NVD Vector: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Exceptional condition
CWE: CWE-755
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

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Timelineinfo

07/20/2011 🔍
11/07/2019 +3032 days 🔍
11/08/2019 +1 days 🔍
02/05/2024 +1550 days 🔍

Sourcesinfo

Vendor: google.com
Product: google.com

Advisory: 40393
Status: Not defined

CVE: CVE-2011-2807 (🔍)
GCVE (CVE): GCVE-0-2011-2807
GCVE (VulDB): GCVE-100-145196
See also: 🔍

Entryinfo

Created: 11/08/2019 09:17
Updated: 02/05/2024 14:03
Changes: 11/08/2019 09:17 (39), 11/08/2019 09:22 (18), 02/05/2024 14:03 (5)
Complete: 🔍
Cache ID: 216::103

Once again VulDB remains the best source 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!