Google Chrome prior 102.0.5005.61 Data Transfer privilege escalation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Google Chrome and classified as problematic. Affected is an unknown function of the component Data Transfer. This manipulation causes an unknown weakness. The identification of this vulnerability is CVE-2022-1867. There is no exploit available. The affected component should be upgraded.
Details
A vulnerability has been found in Google Chrome (Web Browser) and classified as problematic. Affected by this vulnerability is an unknown part of the component Data Transfer. The impact remains unknown.
The weakness was shared 05/26/2022 by Michał Bentkowski. The advisory is shared at chromereleases.googleblog.com. This vulnerability is known as CVE-2022-1867. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 05/26/2022). It is expected to see the exploit prices for this product increasing in the near future.
Upgrading to version 102.0.5005.61 eliminates this vulnerability.
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.5VulDB Meta Temp Score: 5.3
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
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: Privilege escalationCWE: Unknown
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Partially
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 102.0.5005.61
Timeline
05/24/2022 🔍05/26/2022 🔍
05/26/2022 🔍
05/30/2022 🔍
Sources
Vendor: google.comProduct: google.com
Advisory: chromereleases.googleblog.com
Researcher: Michał Bentkowski
Status: Confirmed
CVE: CVE-2022-1867 (🔍)
GCVE (CVE): GCVE-0-2022-1867
GCVE (VulDB): GCVE-100-200749
Entry
Created: 05/26/2022 10:29Updated: 05/30/2022 14:15
Changes: 05/26/2022 10:29 (39), 05/30/2022 14:15 (1)
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.