Google Chrome prior 77.0.3865.75 Omnibox permission assignment
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $5k-$25k | 0.00 |
Summary
A vulnerability identified as critical has been detected in Google Chrome. The impacted element is an unknown function of the component Omnibox. This manipulation causes permission assignment. This vulnerability is tracked as CVE-2019-13659. The attack is possible to be carried out remotely. No exploit exists. You should upgrade the affected component.
Details
A vulnerability classified as critical was found in Google Chrome (Web Browser). Affected by this vulnerability is some unknown functionality of the component Omnibox. The manipulation with an unknown input 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, integrity, and availability. The summary by CVE is:
IDN spoofing in Omnibox in Google Chrome prior to 77.0.3865.75 allowed a remote attacker to perform domain spoofing via IDN homographs via a crafted domain name.
The weakness was disclosed 11/25/2019 as Stable Channel Update for Desktop - September 2019 as confirmed release notes (Website). The advisory is shared at chromereleases.googleblog.com. This vulnerability is known as CVE-2019-13659 since 07/18/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. 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 11/26/2019). 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. A possible mitigation has been published even before and not after the disclosure of the vulnerability.
The entries VDB-146201, VDB-146200, VDB-146199 and VDB-146198 are pretty similar. If you want to get the best quality for vulnerability data then you always have to consider 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.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
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 77.0.3865.75
Timeline
07/18/2019 🔍11/10/2019 🔍
11/25/2019 🔍
11/26/2019 🔍
11/26/2019 🔍
Sources
Vendor: google.comProduct: google.com
Advisory: Stable Channel Update for Desktop - September 2019
Status: Confirmed
CVE: CVE-2019-13659 (🔍)
GCVE (CVE): GCVE-0-2019-13659
GCVE (VulDB): GCVE-100-146197
See also: 🔍
Entry
Created: 11/26/2019 07:02Updated: 11/26/2019 07:07
Changes: 11/26/2019 07:02 (44), 11/26/2019 07:07 (18)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.