Google Chrome prior 118.0.5993.70 Autofill information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.2 | $5k-$25k | 0.00 |
Summary
A vulnerability was found in Google Chrome. It has been classified as problematic. The impacted element is an unknown function of the component Autofill. This manipulation causes information disclosure. This vulnerability is tracked as CVE-2023-5478. The attack is possible to be carried out remotely. No exploit exists. Upgrading the affected component is recommended.
Details
A vulnerability has been found in Google Chrome (Web Browser) and classified as problematic. Affected by this vulnerability is an unknown code block of the component Autofill. The manipulation with an unknown input leads to a information disclosure vulnerability. The CWE definition for the vulnerability is CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. As an impact it is known to affect confidentiality.
The weakness was disclosed 10/11/2023. The advisory is shared at chromereleases.googleblog.com. This vulnerability is known as CVE-2023-5478. 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 10/30/2023). It is expected to see the exploit prices for this product increasing in the near future.MITRE ATT&CK project uses the attack technique T1592 for this issue.
Upgrading to version 118.0.5993.70 eliminates this vulnerability.
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: 4.3VulDB Meta Temp Score: 4.2
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 4.3
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: Information disclosureCWE: CWE-200 / CWE-284 / CWE-266
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 118.0.5993.70
Timeline
10/10/2023 🔍10/11/2023 🔍
10/11/2023 🔍
10/30/2023 🔍
Sources
Vendor: google.comProduct: google.com
Advisory: chromereleases.googleblog.com
Status: Confirmed
CVE: CVE-2023-5478 (🔍)
GCVE (CVE): GCVE-0-2023-5478
GCVE (VulDB): GCVE-100-241897
Entry
Created: 10/11/2023 06:56Updated: 10/30/2023 02:04
Changes: 10/11/2023 06:56 (40), 10/30/2023 01:57 (2), 10/30/2023 02:04 (10)
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.