CVE-2024-20130 json
In power, there is a possible out of bounds write due to a missing bounds check.
published 2024-12-02 23 mo ago modified 2026-06-17 4 mo ago also EUVD-2024-17845
- cvss
- 6.7
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.1%
- EPSS 0.1% chance of exploitation in 30 days, percentile 0%
- public exploits
- 0
- none known
Summary
In power, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS09193374; Issue ID: MSV-1982.
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 23 mo ago
Exploit prediction
0.08% chance of exploitation in the next 30 days, higher than 0% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 6.7 | CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H |
| CNA | 3.1 | 6.7 | CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H |
Affected products
- MediaTek, Inc. MT6739, MT6761, MT6765, MT6768, MT6781, MT6789, MT6833, MT6835, MT6853, MT6855, MT6877, MT6878, MT6879, MT6883, MT6885, MT6886, MT6889, MT6893, MT6895, MT6896, MT6897, MT6983, MT6985, MT6989, MT8195, MT8676, MT8678, MT8696, MT8796
- mediatek mt6739
- mediatek mt6761
- mediatek mt6765
- mediatek mt6768
- mediatek mt6781
- mediatek mt6789
- mediatek mt6833
- mediatek mt6835
- mediatek mt6853
- mediatek mt6855
- mediatek mt6877
- mediatek mt6878
- mediatek mt6879
- mediatek mt6883
- mediatek mt6885
- mediatek mt6886
- mediatek mt6889
- mediatek mt6893
- mediatek mt6895
- mediatek mt6896
- mediatek mt6897
- mediatek mt6983
- mediatek mt6985
- mediatek mt6989
- mediatek mt8195
- mediatek mt8676
- mediatek mt8678
- mediatek mt8696
- mediatek mt8796
Classification
References
-
corp.mediatek.com
/product-security-bulletin/December-2024
vendor-advisory
Sources
- CVE List CVE-2024-20130
- NVD CVE-2024-20130
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.