Google Chrome prior 77.0.3865.75 Downloads HTML Page Address input validation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.2 | $5k-$25k | 0.00 |
Summary
A vulnerability classified as critical has been found in Google Chrome. Affected is an unknown function of the component Downloads. This manipulation as part of HTML Page causes input validation (Address). The identification of this vulnerability is CVE-2019-5875. It is possible to initiate the attack remotely. There is no exploit available. It is recommended to 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 processing of the component Downloads. The manipulation as part of a HTML Page leads to a input validation vulnerability (Address). The CWE definition for the vulnerability is CWE-20. The product receives input or data, but it does
not validate or incorrectly validates that the input has the
properties that are required to process the data safely and
correctly. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
Insufficient data validation in downloads in Google Chrome prior to 77.0.3865.75 allowed a remote attacker to spoof the contents of the Omnibox (URL bar) via a crafted HTML page.
The weakness was shared 11/25/2019. This vulnerability is known as CVE-2019-5875 since 01/09/2019. The attack can be launched remotely. The exploitation doesn't need any form of authentication. 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 02/27/2024). It is expected to see the exploit prices for this product increasing in the near future.
Upgrading to version 77.0.3865.75 eliminates this vulnerability.
The entries VDB-146303, VDB-146302, VDB-146301 and VDB-146300 are related to this item. Statistical analysis made it clear that VulDB provides the best quality 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: 5.3VulDB Meta Temp Score: 5.2
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
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: 🔍
NVD Base Score: 🔍
Exploiting
Name: AddressClass: Input validation / Address
CWE: CWE-20
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 77.0.3865.75
Timeline
01/09/2019 🔍11/25/2019 🔍
11/26/2019 🔍
02/27/2024 🔍
Sources
Vendor: google.comProduct: google.com
Advisory: chromereleases.googleblog.com
Status: Not defined
CVE: CVE-2019-5875 (🔍)
GCVE (CVE): GCVE-0-2019-5875
GCVE (VulDB): GCVE-100-146299
See also: 🔍
Entry
Created: 11/26/2019 08:47Updated: 02/27/2024 16:17
Changes: 11/26/2019 08:47 (41), 11/26/2019 08:52 (18), 02/27/2024 16:17 (4)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.