Google Chrome prior 107.0.5304.121 GPU heap-based overflow

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.0$5k-$25k1.18

A vulnerability has been found in Google Chrome (Web Browser) and classified as critical. This vulnerability affects an unknown functionality of the component GPU. The manipulation with an unknown input leads to a heap-based overflow vulnerability. The CWE definition for the vulnerability is CWE-122. A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc(). As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:

Heap buffer overflow in GPU in Google Chrome prior to 107.0.5304.121 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: High)

The weakness was presented 11/25/2022 by Clement Lecigne with Google (Website). The advisory is shared for download at chromereleases.googleblog.com. This vulnerability was named CVE-2022-4135 since 11/24/2022. Successful exploitation requires user interaction by the victim. Technical details are unknown but an exploit is available. The current price for an exploit might be approx. USD $5k-$25k (estimation calculated on 11/30/2022). It is expected to see the exploit prices for this product increasing in the near future.

It is declared as highly functional.

Upgrading to version 107.0.5304.121 eliminates this vulnerability. The upgrade is hosted for download at chromereleases.googleblog.com.

Productinfo

Type

Vendor

Name

License

  • free

CPE 2.3info

CPE 2.2info

Video

CVSSv3info

VulDB Meta Base Score: 6.3
VulDB Meta Temp Score: 6.0

VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
🔍🔍🔍🔍🔍🔍
🔍🔍🔍🔍🔍🔍
🔍🔍🔍🔍🔍🔍
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
unlockunlockunlockunlockunlockunlock
unlockunlockunlockunlockunlockunlock
unlockunlockunlockunlockunlockunlock

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

Exploitinginfo

Class: Heap-based overflow
CWE: CWE-122 / CWE-119
ATT&CK: Unknown

Local: No
Remote: Yes

Availability: 🔒
Status: Highly functional

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: 🔒

Upgrade: Chrome 107.0.5304.121

Timelineinfo

11/24/2022 CVE reserved
11/25/2022 +1 days Advisory disclosed
11/25/2022 +0 days VulDB entry created
11/30/2022 +5 days VulDB last update

Sourcesinfo

Vendor: google.com
Product: google.com

Advisory: chromereleases.googleblog.com
Researcher: Clement Lecigne
Organization: Google
Status: Confirmed
Confirmation: 🔒

CVE: CVE-2022-4135 (🔒)
scip Labs: https://www.scip.ch/en/?labs.20161013

Entryinfo

Created: 11/25/2022 08:14 AM
Updated: 11/30/2022 05:02 PM
Changes: 11/25/2022 08:14 AM (42), 11/30/2022 05:02 PM (7)
Complete: 🔍

Discussion

No comments yet. Languages: en.

Please log in to comment.

Do you know our Splunk app?

Download it now for free!