Samsung Galaxy S6 SM-G920F G920FXXU5EQH7 bcmdhd4358 Wi-Fi Driver dhd_linux.c dhd_rx_frame memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in Samsung Galaxy S6 SM-G920F G920FXXU5EQH7. Affected is the function dhd_rx_frame of the file drivers/net/wireless/bcmdhd4358/dhd_linux.c of the component bcmdhd4358 Wi-Fi Driver. This manipulation causes memory corruption.
This vulnerability is tracked as CVE-2018-14852. The attack is only possible within the local network. No exploit exists.
Details
A vulnerability classified as critical was found in Samsung Galaxy S6 SM-G920F G920FXXU5EQH7 (Smartphone Operating System). Affected by this vulnerability is the function dhd_rx_frame of the file drivers/net/wireless/bcmdhd4358/dhd_linux.c of the component bcmdhd4358 Wi-Fi Driver. The manipulation with an unknown input leads to a memory corruption vulnerability. The CWE definition for the vulnerability is CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
Out-of-bounds array access in dhd_rx_frame in drivers/net/wireless/bcmdhd4358/dhd_linux.c in the bcmdhd4358 Wi-Fi driver on the Samsung Galaxy S6 SM-G920F G920FXXU5EQH7 allows an attacker (who has obtained code execution on the Wi-Fi chip) to cause invalid accesses to operating system memory due to improper validation of the network interface index provided by the Wi-Fi chip's firmware.
The bug was discovered 12/11/2018. The weakness was disclosed 12/17/2018 (Website). The advisory is shared at github.com. This vulnerability is known as CVE-2018-14852 since 08/02/2018. The attack can only be done within the local network. The exploitation doesn't need any form of authentication. Technical details are known, but no exploit is available.
The vulnerability was handled as a non-public zero-day exploit for at least 6 days. During that time the estimated underground price was around $0-$5k.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The entries VDB-128021, VDB-128020, VDB-128019 and VDB-128018 are pretty similar. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.samsung.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 6.3
VulDB Base Score: 6.3
VulDB Temp Score: 6.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.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: Memory corruptionCWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Partially
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
08/02/2018 🔍12/11/2018 🔍
12/17/2018 🔍
12/17/2018 🔍
12/18/2018 🔍
04/21/2020 🔍
Sources
Vendor: samsung.comAdvisory: github.com
Status: Not defined
CVE: CVE-2018-14852 (🔍)
GCVE (CVE): GCVE-0-2018-14852
GCVE (VulDB): GCVE-100-128017
See also: 🔍
Entry
Created: 12/18/2018 07:51Updated: 04/21/2020 10:56
Changes: 12/18/2018 07:51 (60), 04/21/2020 10:56 (1)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.