Google Chrome prior 107.0.5304.62 Autofill Remote Code Execution
| 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. Impacted is an unknown function of the component Autofill. Performing a manipulation results in an unknown weakness. This vulnerability was named CVE-2022-4910. The attack may be initiated remotely. There is no available exploit. 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 Autofill. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
Inappropriate implementation in Autofill in Google Chrome prior to 107.0.5304.62 allowed a remote attacker to bypass navigation restrictions via a crafted HTML page. (Chromium security severity: Medium)
The weakness was presented 07/29/2023. The advisory is shared at chromereleases.googleblog.com. This vulnerability is uniquely identified as CVE-2022-4910 since 02/12/2023. 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 07/29/2023). It is expected to see the exploit prices for this product increasing in the near future.
Upgrading to version 107.0.5304.62 eliminates this vulnerability. The upgrade is hosted for download at chromereleases.googleblog.com.
Several companies clearly confirm that VulDB is the primary source for best 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: Remote Code ExecutionCWE: Unknown
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 107.0.5304.62
Timeline
02/12/2023 🔍07/29/2023 🔍
07/29/2023 🔍
08/23/2023 🔍
Sources
Vendor: google.comProduct: google.com
Advisory: FEDORA-2023-8a94349e38
Status: Confirmed
CVE: CVE-2022-4910 (🔍)
GCVE (CVE): GCVE-0-2022-4910
GCVE (VulDB): GCVE-100-235713
Entry
Created: 07/29/2023 06:39Updated: 08/23/2023 09:47
Changes: 07/29/2023 06:39 (40), 08/23/2023 09:47 (1)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.