Google Chrome prior 108.0.5359.124 Blink Media use after free
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.4 | $5k-$25k | 0.00 |
Summary
A vulnerability identified as critical has been detected in Google Chrome. The impacted element is an unknown function of the component Blink Media. Performing a manipulation results in use after free. This vulnerability is known as CVE-2022-4436. Remote exploitation of the attack is possible. No exploit is available. You should upgrade the affected component.
Details
A vulnerability, which was classified as critical, was found in Google Chrome (Web Browser). This affects some unknown functionality of the component Blink Media. The manipulation with an unknown input leads to a use after free vulnerability. CWE is classifying the issue as CWE-416. Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code. This is going to have an impact on confidentiality, integrity, and availability.
The weakness was published 12/14/2022. The advisory is shared at chromereleases.googleblog.com. This vulnerability is uniquely identified as CVE-2022-4436. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 01/12/2023). It is expected to see the exploit prices for this product increasing in the near future.
Upgrading to version 108.0.5359.124 eliminates this vulnerability.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
License
Website
- Vendor: https://www.google.com/
- Product: https://www.google.com/chrome/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.6VulDB Meta Temp Score: 7.4
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.8
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Use after freeCWE: CWE-416 / CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Bug Bounty Price: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Chrome 108.0.5359.124
Timeline
12/12/2022 🔍12/14/2022 🔍
12/14/2022 🔍
01/12/2023 🔍
Sources
Vendor: google.comProduct: google.com
Advisory: chromereleases.googleblog.com
Status: Confirmed
CVE: CVE-2022-4436 (🔍)
GCVE (CVE): GCVE-0-2022-4436
GCVE (VulDB): GCVE-100-215805
Entry
Created: 12/14/2022 12:22Updated: 01/12/2023 14:56
Changes: 12/14/2022 12:22 (39), 01/12/2023 14:55 (2), 01/12/2023 14:56 (11)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.