CVE-2024-20078 json
In venc, there is a possible out of bounds write due to type confusion.
published 2y ago modified 4mo ago also EUVD-2024-17793
- cvss
- 9.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 18%
- public exploits
- 0
- none known
Summary
In venc, there is a possible out of bounds write due to type confusion. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS08737250; Issue ID: MSV-1452.
Is CVE-2024-20078 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
- Assessed
- 2y ago
Exploit prediction
0.26% chance of exploitation in the next 30 days, higher than 18% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| CNA | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected products
- MediaTek, Inc. MT6768, MT6779, MT8321, MT8385, MT8755, MT8765, MT8766, MT8768, MT8771, MT8775, MT8781, MT8786, MT8788, MT8789, MT8791T, MT8792, MT8795T, MT8796, MT8797, MT8798
- mediatek mt6768
- mediatek mt6779
- mediatek mt8321
- mediatek mt8385
- mediatek mt8755
- mediatek mt8765
- mediatek mt8766
- mediatek mt8768
- mediatek mt8771
- mediatek mt8775
- mediatek mt8781
- mediatek mt8786
- mediatek mt8788
- mediatek mt8789
- mediatek mt8791t
- mediatek mt8792
- mediatek mt8795t
- mediatek mt8796
- mediatek mt8797
- mediatek mt8798
- google android
Classification
- Weakness
-
- CWE-843 Access of Resource Using Incompatible Type
References
-
corp.mediatek.com
/product-security-bulletin/July-2024
vendor-advisory
Sources
- CVE List CVE-2024-20078
- NVD CVE-2024-20078
Fencer Intel 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.