| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.2 | $5k-$25k | 0.00 |
Summary
A vulnerability, which was classified as critical, was found in Google Chrome up to 73. Affected by this issue is some unknown functionality of the component Blink. Executing a manipulation as part of HTML Page can lead to use after free. This vulnerability is handled as CVE-2019-5787. The attack can be executed remotely. There is not any exploit available. You should upgrade the affected component.
Details
A vulnerability was found in Google Chrome up to 73 (Web Browser). It has been declared as critical. This vulnerability affects some unknown functionality of the component Blink. The manipulation as part of a HTML Page 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. CVE summarizes:
Use-after-garbage-collection in Blink in Google Chrome prior to 73.0.3683.75 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
The bug was discovered 03/12/2019. The weakness was released 05/23/2019 (Website). The advisory is available at lists.opensuse.org. This vulnerability was named CVE-2019-5787 since 01/09/2019. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. Successful exploitation requires user interaction by the victim. The technical details are unknown and an exploit is not available. The structure of the vulnerability defines a possible price range of USD $5k-$25k at the moment (estimation calculated on 06/15/2020). It is expected to see the exploit prices for this product increasing in the near future.
The vulnerability was handled as a non-public zero-day exploit for at least 72 days. During that time the estimated underground price was around $25k-$100k. The commercial vulnerability scanner Qualys is able to test this issue with plugin 371692 (Google Chrome Prior To 73.0.3683.75 Multiple Vulnerability).
Upgrading to version 73.0.3683.75 eliminates this vulnerability.
Entries connected to this vulnerability are available at VDB-135467, VDB-135468, VDB-135469 and VDB-135470. If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Type
Vendor
Name
Version
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: 7.6VulDB Meta Temp Score: 7.4
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.8
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
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 |
Qualys ID: 🔍
Qualys Name: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Chrome 73.0.3683.75
Timeline
01/09/2019 🔍03/12/2019 🔍
05/23/2019 🔍
05/24/2019 🔍
06/15/2020 🔍
Sources
Vendor: google.comProduct: google.com
Advisory: lists.opensuse.org
Status: Confirmed
CVE: CVE-2019-5787 (🔍)
GCVE (CVE): GCVE-0-2019-5787
GCVE (VulDB): GCVE-100-135466
See also: 🔍
Entry
Created: 05/24/2019 21:59Updated: 06/15/2020 11:24
Changes: 05/24/2019 21:59 (63), 06/15/2020 11:24 (2)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.