CVE-2020-8860
Summary
| CVE | CVE-2020-8860 |
|---|---|
| State | PUBLIC |
| Assigner | [email protected] |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2020-02-22 00:15:00 UTC |
| Updated | 2020-03-05 18:49:00 UTC |
| Description | This vulnerability allows remote attackers to execute arbitrary code on affected installations of Samsung Galaxy S10 Firmware G973FXXS3ASJA, O(8.x), P(9.0), Q(10.0) devices with Exynos chipsets. User interaction is required to exploit this vulnerability in that the target must answer a phone call. The specific flaw exists within the Call Control Setup messages. The issue results from the lack of proper validation of the length of user-supplied data prior to copying it to a fixed-length, stack-based buffer. An attacker can leverage this vulnerability to execute code in the context of the baseband processor. Was ZDI-CAN-9658. |
Risk And Classification
Problem Types: CWE-787
NVD Known Affected Configurations (CPE 2.3)
| Type | Vendor | Product | Version | Update | Edition | Language |
|---|---|---|---|---|---|---|
| Operating System | Android | 10.0 | All | All | All | |
| Operating System | Android | 8.0 | All | All | All | |
| Operating System | Android | 8.1 | All | All | All | |
| Operating System | Android | 9.0 | All | All | All | |
| Operating System | Android | 10.0 | All | All | All | |
| Operating System | Android | 8.0 | All | All | All | |
| Operating System | Android | 8.1 | All | All | All | |
| Operating System | Android | 9.0 | All | All | All | |
| Hardware | Samsung | Galaxy S10 | All | All | All | All |
| Hardware | Samsung | Galaxy S10 | All | All | All | All |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| Samsung Mobile Security | N/A | security.samsungmobile.com | Vendor Advisory |
| ZDI-20-255 | Zero Day Initiative | N/A | www.zerodayinitiative.com | Third Party Advisory, VDB Entry |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.