MediaTek MT8678 Android 13.0 up to SDK release 3.3 Bluetooth Firmware assertion
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.8 | $0-$5k | 0.00 |
Summary
A vulnerability was found in MediaTek MT2737, MT3605, MT6985, MT6989, MT6990, MT7925, MT7927, MT8518S, MT8532 and MT8678 Android 13.0 up to SDK release 3.3. It has been rated as problematic. Affected by this vulnerability is an unknown functionality of the component Bluetooth Firmware. The manipulation leads to assertion. This vulnerability is uniquely identified as CVE-2024-20139. Local access is required to approach this attack. No exploit exists. Applying a patch is the recommended action to fix this issue.
Details
A vulnerability, which was classified as problematic, has been found in MediaTek MT2737, MT3605, MT6985, MT6989, MT6990, MT7925, MT7927, MT8518S, MT8532 and MT8678 Android 13.0 up to SDK release 3.3. This issue affects an unknown function of the component Bluetooth Firmware. The manipulation with an unknown input leads to a assertion vulnerability. Using CWE to declare the problem leads to CWE-617. The product contains an assert() or similar statement that can be triggered by an attacker, which leads to an application exit or other behavior that is more severe than necessary. Impacted is availability. The summary by CVE is:
In Bluetooth firmware, there is a possible firmware asssert due to improper handling of exceptional conditions. This could lead to local denial of service with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS09001270; Issue ID: MSV-1600.
The advisory is shared at corp.mediatek.com. The identification of this vulnerability is CVE-2024-20139 since 11/02/2023. The exploitation is known to be easy. An attack has to be approached locally. Neither technical details nor an exploit are publicly available.
Applying the patch ALPS09001270 is able to eliminate this problem.
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: 4.9VulDB Meta Temp Score: 4.8
VulDB Base Score: 3.3
VulDB Temp Score: 3.2
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 6.5
CNA Vector (MediaTek): 🔍
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: AssertionCWE: CWE-617
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
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: PatchStatus: 🔍
0-Day Time: 🔍
Patch: ALPS09001270
Timeline
11/02/2023 🔍12/02/2024 🔍
12/02/2024 🔍
12/02/2024 🔍
Sources
Advisory: MSV-1600Status: Confirmed
CVE: CVE-2024-20139 (🔍)
GCVE (CVE): GCVE-0-2024-20139
GCVE (VulDB): GCVE-100-286517
Entry
Created: 12/02/2024 07:39Updated: 12/02/2024 20:04
Changes: 12/02/2024 07:39 (56), 12/02/2024 13:06 (1), 12/02/2024 20:04 (11)
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.