Google Chrome prior 102.0.5005.61 Performance Manager use after free
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $5k-$25k | 0.00 |
Summary
A vulnerability identified as critical has been detected in Google Chrome. This affects an unknown part of the component Performance Manager. The manipulation leads to use after free. This vulnerability is documented as CVE-2022-1859. There is not any exploit available. You should upgrade the affected component.
Details
A vulnerability was found in Google Chrome (Web Browser) and classified as critical. This issue affects some unknown functionality of the component Performance Manager. The manipulation with an unknown input leads to a use after free vulnerability. Using CWE to declare the problem leads to CWE-416. Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code. Impacted is confidentiality, integrity, and availability.
The weakness was released 05/26/2022 by Guannan Wang. The advisory is shared at chromereleases.googleblog.com. The identification of this vulnerability is CVE-2022-1859. 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 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: Use after freeCWE: CWE-416 / CWE-119
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: Guannan Wang
Status: Confirmed
CVE: CVE-2022-1859 (🔍)
GCVE (CVE): GCVE-0-2022-1859
GCVE (VulDB): GCVE-100-200741
Entry
Created: 05/26/2022 10:25Updated: 05/30/2022 13:41
Changes: 05/26/2022 10:25 (41), 05/30/2022 13:41 (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.