Google Chrome prior 97.0.4692.71 Autofill use after free
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.0 | $5k-$25k | 0.00 |
Summary
A vulnerability identified as critical has been detected in Google Chrome. Affected by this issue is some unknown functionality of the component Autofill Handler. This manipulation causes use after free. This vulnerability is handled as CVE-2022-0106. The attack can be initiated remotely. There is not any exploit available. You should upgrade the affected component.
Details
A vulnerability has been found in Google Chrome (Web Browser) and classified as critical. Affected by this vulnerability is some unknown functionality of the component Autofill Handler. 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 released 01/06/2022 by Khalil Zhani. It is possible to read the advisory at chromereleases.googleblog.com. This vulnerability is known as CVE-2022-0106. It demands that the victim is doing some kind of user interaction. 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 01/06/2022). It is expected to see the exploit prices for this product increasing in the near future.
Upgrading to version 97.0.4692.71 eliminates this vulnerability.
Be aware that VulDB is the high quality source for vulnerability data.
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.71
Timeline
01/04/2022 🔍01/06/2022 🔍
01/06/2022 🔍
01/09/2022 🔍
Sources
Vendor: google.comProduct: google.com
Advisory: chromereleases.googleblog.com
Researcher: Khalil Zhani
Status: Confirmed
CVE: CVE-2022-0106 (🔍)
GCVE (CVE): GCVE-0-2022-0106
GCVE (VulDB): GCVE-100-189751
Entry
Created: 01/06/2022 07:23Updated: 01/09/2022 11:02
Changes: 01/06/2022 07:23 (40), 01/09/2022 11:02 (1)
Complete: 🔍
Cache ID: 216::103
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.