Skip to content
Fencer Vulns
medium 6.6

CVE-2024-20042 json

In da, there is a possible out of bounds write due to a missing bounds check.

published 2024-04-01 2 y ago modified 2026-06-17 4 mo ago also EUVD-2024-17757

cvss
6.6
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 19%
public exploits
0
none known

Summary

In da, 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: ALPS08541780; Issue ID: ALPS08541780.

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
2 y ago

Exploit prediction

0.27% chance of exploitation in the next 30 days, higher than 19% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CISA ADP 3.1 6.6 CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H
CNA 3.1 6.6 CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H

Affected products

  • MediaTek, Inc. MT6739, MT6757, MT6761, MT6763, MT6765, MT6768, MT6771, MT6779, MT6781, MT6785, MT6833, MT6853, MT6873, MT6877, MT6885, MT6893, MT8167, MT8168, MT8173, MT8175, MT8183, MT8195, MT8321, MT8362A, MT8365, MT8385, MT8395, MT8666, MT8673, MT8678, MT8765, MT8766, MT8768, MT8781, MT8786, MT8788, MT8789, MT8791, MT8791T, MT8796, MT8797, MT8798
  • mediatek mt6739
  • mediatek mt6757
  • mediatek mt6761
  • mediatek mt6763
  • mediatek mt6765
  • mediatek mt6768
  • mediatek mt6771
  • mediatek mt6779
  • mediatek mt6781
  • mediatek mt6785
  • mediatek mt6833
  • mediatek mt6853
  • mediatek mt6873
  • mediatek mt6877
  • mediatek mt6885
  • mediatek mt6893
  • mediatek mt8167
  • mediatek mt8168
  • mediatek mt8173
  • mediatek mt8175
  • mediatek mt8183
  • mediatek mt8195
  • mediatek mt8321
  • mediatek mt8362a
  • mediatek mt8365
  • mediatek mt8385
  • mediatek mt8395
  • mediatek mt8666
  • mediatek mt8673

Classification

Weakness

References

Sources

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.