CVE-2023-32873 json
In keyInstall, there is a possible out of bounds write due to a missing bounds check.
published 2024-05-06 2 y ago modified 2026-06-17 4 mo ago also EUVD-2023-37094
- cvss
- 6.4
- 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 keyInstall, 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: ALPS08583919; Issue ID: ALPS08304227.
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 2 y 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.4 | CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H |
| NVD | 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.4 | CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H |
Affected products
- MediaTek, Inc. MT6761, MT6765, MT6768, MT6833, MT6853, MT6855, MT6893, MT6895, MT6983, MT8321, MT8385, MT8755, MT8765, MT8766, MT8768, MT8771, MT8781, MT8786, MT8788, MT8789, MT8791T, MT8792, MT8795T, MT8796
- mediatek mt6761
- mediatek mt6765
- mediatek mt6768
- mediatek mt6833
- mediatek mt6853
- mediatek mt6855
- mediatek mt6893
- mediatek mt6895
- mediatek mt6983
- mediatek mt8321
- mediatek mt8385
- mediatek mt8755
- mediatek mt8765
- mediatek mt8766
- mediatek mt8768
- mediatek mt8771
- mediatek mt8781
- mediatek mt8786
- mediatek mt8788
- mediatek mt8789
- mediatek mt8791t
- mediatek mt8792
- mediatek mt8795t
- mediatek mt8796
Classification
- Weakness
-
- CWE-787 Out-of-bounds Write
References
-
corp.mediatek.com
/product-security-bulletin/May-2024
vendor-advisory
Sources
- CVE List CVE-2023-32873
- NVD CVE-2023-32873
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.