Google Chrome prior 85.0.4183.83 Blink HTML Page permission assignment
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $5k-$25k | 0.00 |
Summary
A vulnerability described as problematic has been identified in Google Chrome. This impacts an unknown function of the component Blink. Executing a manipulation as part of HTML Page can lead to permission assignment. This vulnerability appears as CVE-2020-6562. The attack may be performed from remote. There is no available exploit. Upgrading the affected component is recommended.
Details
A vulnerability has been found in Google Chrome (Web Browser) and classified as problematic. This vulnerability affects an unknown code block of the component Blink. The manipulation as part of a HTML Page leads to a permission assignment vulnerability. The CWE definition for the vulnerability is CWE-732. The product specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors. As an impact it is known to affect confidentiality. CVE summarizes:
Insufficient policy enforcement in Blink in Google Chrome prior to 85.0.4183.83 allowed a remote attacker to leak cross-origin data via a crafted HTML page.
The weakness was presented 09/21/2020 (Website). The advisory is available at chromereleases.googleblog.com. This vulnerability was named CVE-2020-6562 since 01/08/2020. 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 09/22/2020). It is expected to see the exploit prices for this product increasing in the near future.
Upgrading to version 85.0.4183.83 eliminates this vulnerability.
See VDB-161694, VDB-161695, VDB-161696 and VDB-161697 for similar entries. If you want to get best quality of vulnerability data, you may have to visit VulDB.
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.4VulDB Meta Temp Score: 5.3
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.5
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: Permission assignmentCWE: CWE-732 / CWE-275 / CWE-266
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 85.0.4183.83
Timeline
01/08/2020 🔍09/21/2020 🔍
09/22/2020 🔍
09/22/2020 🔍
Sources
Vendor: google.comProduct: google.com
Advisory: chromereleases.googleblog.com
Status: Not defined
CVE: CVE-2020-6562 (🔍)
GCVE (CVE): GCVE-0-2020-6562
GCVE (VulDB): GCVE-100-161698
See also: 🔍
Entry
Created: 09/22/2020 06:54Updated: 09/22/2020 06:59
Changes: 09/22/2020 06:54 (42), 09/22/2020 06:59 (18)
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.