Skip to content
Fencer Vulns
medium 6.7

CVE-2024-20131 json

In Modem, there is a possible escalation of privilege due to an incorrect bounds check.

published 2024-12-02 23 mo ago modified 2026-06-17 4 mo ago also EUVD-2024-17846

cvss
6.7
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 7%
public exploits
0
none known

Summary

In Modem, there is a possible escalation of privilege due to an incorrect bounds check. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation. Patch ID: MOLY01395886; Issue ID: MSV-1873.

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
23 mo ago

Exploit prediction

0.18% chance of exploitation in the next 30 days, higher than 7% 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. MT2737, MT2739, MT6789, MT6813, MT6815, MT6835, MT6835T, MT6855, MT6878, MT6878T, MT6879, MT6886, MT6895, MT6895T, MT6896, MT6897, MT6899, MT6980, MT6980D, MT6983, MT6985, MT6986, MT6986D, MT6988, MT6989, MT6990, MT6991, MT8673, MT8676, MT8795T, MT8798
  • mediatek mt2737
  • mediatek mt2739
  • mediatek mt6789
  • mediatek mt6813
  • mediatek mt6815
  • mediatek mt6835
  • mediatek mt6835t
  • mediatek mt6855
  • mediatek mt6878
  • mediatek mt6878t
  • mediatek mt6879
  • mediatek mt6886
  • mediatek mt6895
  • mediatek mt6895t
  • mediatek mt6896
  • mediatek mt6897
  • mediatek mt6899
  • mediatek mt6980
  • mediatek mt6980d
  • mediatek mt6983
  • mediatek mt6985
  • mediatek mt6986
  • mediatek mt6986d
  • mediatek mt6988
  • mediatek mt6989
  • mediatek mt6990
  • mediatek mt6991
  • mediatek mt8673
  • mediatek mt8676
  • mediatek mt8795t
  • mediatek mt8798

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.