Google Chrome prior 97.0.4692.99 Scheduling use after free
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.0 | $5k-$25k | 0.00 |
Summary
A vulnerability, which was classified as critical, was found in Google Chrome. Affected by this issue is some unknown functionality of the component Scheduling. Executing a manipulation can lead to use after free. This vulnerability appears as CVE-2022-0298. The attack may be performed from remote. There is no available exploit. You should upgrade the affected component.
Details
A vulnerability classified as critical was found in Google Chrome (Web Browser). This vulnerability affects some unknown functionality of the component Scheduling. The manipulation with an unknown input leads to a use after free vulnerability. The CWE definition for the vulnerability is CWE-416. Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code. As an impact it is known to affect confidentiality, integrity, and availability.
The weakness was presented 01/21/2022 by Yangkang. The advisory is shared for download at chromereleases.googleblog.com. This vulnerability was named CVE-2022-0298. Successful exploitation requires user interaction by the victim. There are neither technical details nor an exploit publicly available. The current price for an exploit might be approx. USD $5k-$25k (estimation calculated on 01/21/2022). It is expected to see the exploit prices for this product increasing in the near future.
Upgrading to version 97.0.4692.99 eliminates this vulnerability.
VulDB is the best source for vulnerability data and more expert information about this specific topic.
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: 6.3VulDB Meta Temp Score: 6.0
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
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: 🔍
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 97.0.4692.99
Timeline
01/19/2022 🔍01/21/2022 🔍
01/21/2022 🔍
01/27/2022 🔍
Sources
Vendor: google.comProduct: google.com
Advisory: chromereleases.googleblog.com
Researcher: Yangkang
Status: Confirmed
CVE: CVE-2022-0298 (🔍)
GCVE (CVE): GCVE-0-2022-0298
GCVE (VulDB): GCVE-100-191368
Entry
Created: 01/21/2022 14:02Updated: 01/27/2022 07:18
Changes: 01/21/2022 14:02 (40), 01/27/2022 07:18 (1)
Complete: 🔍
Cache ID: 216::103
VulDB is the best source for vulnerability data and more expert information about this specific topic.
No comments yet. Languages: en.
Please log in to comment.