Google Android 8.0/8.1/9.0/10.0 proxy_resolver_v8.cc SetPacScript use after free

CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
8.4 | $5k-$25k | 0.00 |
Summary
A vulnerability, which was classified as critical, was found in Google Android 8.0/8.1/9.0/10.0. Affected is the function ProxyResolverV8::SetPacScript
of the file proxy_resolver_v8.cc. The manipulation leads to use after free.
This vulnerability is traded as CVE-2019-2205. It is possible to launch the attack remotely. There is no exploit available.
It is recommended to apply a patch to fix this issue.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Details
A vulnerability, which was classified as critical, has been found in Google Android 8.0/8.1/9.0/10.0 (Smartphone Operating System). This issue affects the function ProxyResolverV8::SetPacScript
of the file proxy_resolver_v8.cc. 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 summary by CVE is:
In ProxyResolverV8::SetPacScript of proxy_resolver_v8.cc, there is a possible memory corruption due to a use after free. This could lead to remote code execution with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-8.0 Android-8.1 Android-9 Android-10Android ID: A-139806216
The weakness was presented 11/13/2019. The identification of this vulnerability is CVE-2019-2205 since 12/10/2018. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 02/13/2024). It is expected to see the exploit prices for this product increasing in the near future.
Applying a patch is able to eliminate this problem.
See VDB-145527, VDB-145526, VDB-145525 and VDB-145524 for similar entries. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.5VulDB Meta Temp Score: 8.4
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.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: 🔍
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: PatchStatus: 🔍
0-Day Time: 🔍
Timeline
12/10/2018 🔍11/13/2019 🔍
11/14/2019 🔍
02/13/2024 🔍
Sources
Vendor: google.comAdvisory: source.android.com
Status: Not defined
CVE: CVE-2019-2205 (🔍)
GCVE (CVE): GCVE-0-2019-2205
GCVE (VulDB): GCVE-100-145523
scip Labs: https://www.scip.ch/en/?labs.20150917
See also: 🔍
Entry
Created: 11/14/2019 04:26 PMUpdated: 02/13/2024 05:26 PM
Changes: 11/14/2019 04:26 PM (39), 11/14/2019 04:31 PM (18), 02/13/2024 05:26 PM (4)
Complete: 🔍
Cache ID: 18:F93:40
No comments yet. Languages: en.
Please log in to comment.