Broadcom Firmware on Nexus 5/Raspberry Pi 3 LMP Command access control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.5 | $0-$5k | 0.00 |
Summary
A vulnerability categorized as critical has been discovered in Broadcom Firmware on Nexus 5/Raspberry Pi 3. This vulnerability affects unknown code of the component LMP Command Handler. Such manipulation leads to access control. This vulnerability is uniquely identified as CVE-2018-19860. The attack can only be initiated within the local network. No exploit exists.
Details
A vulnerability, which was classified as critical, has been found in Broadcom Firmware on Nexus 5/Raspberry Pi 3 (Firmware Software) (affected version unknown). Affected by this issue is an unknown functionality of the component LMP Command Handler. The manipulation with an unknown input leads to a access control vulnerability. Using CWE to declare the problem leads to CWE-264. Impacted is confidentiality, integrity, and availability. CVE summarizes:
Broadcom firmware before summer 2014 on Nexus 5 BCM4335C0 2012-12-11, Raspberry Pi 3 BCM43438A1 2014-06-02, and unspecifed other devices does not properly restrict LMP commnds and executes certain memory contents upon receiving an LMP command, as demonstrated by executing an HCI command.
The weakness was disclosed 06/07/2019 (Website). The advisory is shared for download at source.android.com. This vulnerability is handled as CVE-2018-19860 since 12/05/2018. The exploitation is known to be easy. The attack can only be done within the local network. No form of authentication is required for exploitation. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1068.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The entries VDB-134453, VDB-134495, VDB-134496 and VDB-134497 are pretty similar. Once again VulDB remains the best source for vulnerability data.
Product
Type
Vendor
Name
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.6VulDB Meta Temp Score: 7.6
VulDB Base Score: 6.3
VulDB Temp Score: 6.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.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: Access controlCWE: CWE-264
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
12/05/2018 🔍06/07/2019 🔍
06/08/2019 🔍
06/21/2020 🔍
Sources
Advisory: source.android.comStatus: Not defined
Confirmation: 🔍
CVE: CVE-2018-19860 (🔍)
GCVE (CVE): GCVE-0-2018-19860
GCVE (VulDB): GCVE-100-136172
See also: 🔍
Entry
Created: 06/08/2019 07:26Updated: 06/21/2020 09:32
Changes: 06/08/2019 07:26 (56), 06/21/2020 09:32 (1)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.