| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in MediaTek MT6580, MT6739, MT6761, MT6765, MT6768, MT6779, MT6781, MT6785, MT6789, MT6833, MT6835, MT6853, MT6855, MT6873, MT6877, MT6879, MT6883, MT6885, MT6886, MT6889, MT6893, MT6895, MT6983, MT6985, MT6989, MT8321, MT8673, MT8765, MT8766, MT8768, MT8781, MT8789, MT8791, MT8792 and MT8796. The affected element is an unknown function of the component Aee. This manipulation causes permission. This vulnerability appears as CVE-2024-20032. The attack requires local access. There is no available exploit. Applying a patch is the recommended action to fix this issue.
Details
A vulnerability has been found in MediaTek MT6580, MT6739, MT6761, MT6765, MT6768, MT6779, MT6781, MT6785, MT6789, MT6833, MT6835, MT6853, MT6855, MT6873, MT6877, MT6879, MT6883, MT6885, MT6886, MT6889, MT6893, MT6895, MT6983, MT6985, MT6989, MT8321, MT8673, MT8765, MT8766, MT8768, MT8781, MT8789, MT8791, MT8792 and MT8796 (Chip Software) and classified as critical. Affected by this vulnerability is an unknown functionality of the component Aee. The manipulation with an unknown input leads to a permission vulnerability. The CWE definition for the vulnerability is CWE-275. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
In aee, there is a possible permission bypass due to a missing permission check. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS08487630; Issue ID: MSV-1020.
The weakness was presented 03/04/2024 as ALPS08487630. The advisory is shared at corp.mediatek.com. This vulnerability is known as CVE-2024-20032 since 11/02/2023. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1222 for this issue.
Applying the patch ALPS08487630 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
- MT6580
- MT6739
- MT6761
- MT6765
- MT6768
- MT6779
- MT6781
- MT6785
- MT6789
- MT6833
- MT6835
- MT6853
- MT6855
- MT6873
- MT6877
- MT6879
- MT6883
- MT6885
- MT6886
- MT6889
- MT6893
- MT6895
- MT6983
- MT6985
- MT6989
- MT8321
- MT8673
- MT8765
- MT8766
- MT8768
- MT8781
- MT8789
- MT8791
- MT8792
- MT8796
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.4VulDB Meta Temp Score: 5.3
VulDB Base Score: 4.2
VulDB Temp Score: 4.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 6.7
CNA 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: 🔍
Exploiting
Class: PermissionCWE: CWE-275 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
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: ALPS08487630
Timeline
11/02/2023 🔍03/04/2024 🔍
03/04/2024 🔍
08/23/2024 🔍
Sources
Advisory: ALPS08487630Status: Confirmed
CVE: CVE-2024-20032 (🔍)
GCVE (CVE): GCVE-0-2024-20032
GCVE (VulDB): GCVE-100-255613
Entry
Created: 03/04/2024 07:47Updated: 08/23/2024 22:32
Changes: 03/04/2024 07:47 (41), 08/23/2024 22:32 (27)
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.