Skip to content
Fencer Vulns
medium 6.7

CVE-2024-20022 json

In lk, there is a possible escalation of privilege due to a missing bounds check.

published 2024-03-04 2 y ago modified 2026-06-17 4 mo ago also EUVD-2024-17737

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 2%
public exploits
0
none known

Summary

In lk, there is a possible escalation of privilege 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: ALPS08528255; Issue ID: ALPS08528255.

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
2 y ago

Exploit prediction

0.12% chance of exploitation in the next 30 days, higher than 2% 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
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.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, MT6789, MT6835, MT6855, MT6879, MT6880, MT6886, MT6890, MT6895, MT6980, MT6983, MT6985, MT6989, MT6990, MT8321, MT8385, MT8666, MT8667, MT8673, MT8765, MT8766, MT8768, MT8781, MT8786, MT8788, MT8789, MT8791, MT8796, MT8797, MT8798
  • mediatek mt2737
  • mediatek mt6789
  • mediatek mt6835
  • mediatek mt6855
  • mediatek mt6879
  • mediatek mt6880
  • mediatek mt6886
  • mediatek mt6890
  • mediatek mt6895
  • mediatek mt6980
  • mediatek mt6983
  • mediatek mt6985
  • mediatek mt6989
  • mediatek mt6990
  • mediatek mt8321
  • mediatek mt8385
  • mediatek mt8666
  • mediatek mt8667
  • mediatek mt8673
  • mediatek mt8765
  • mediatek mt8766
  • mediatek mt8768
  • mediatek mt8781
  • mediatek mt8786
  • mediatek mt8788
  • mediatek mt8789
  • mediatek mt8791
  • mediatek mt8796
  • mediatek mt8797
  • 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.