Skip to content
Fencer Vulns
medium 6.7

CVE-2024-20037 json

In pq, there is a possible write-what-where condition due to an incorrect bounds check.

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

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

Summary

In pq, there is a possible write-what-where condition 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: ALPS08495937; Issue ID: ALPS08495937.

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
2 y ago

Exploit prediction

0.09% 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.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. MT6739, MT6761, MT6765, MT6768, MT6779, MT6781, MT6785, MT6789, MT6833, MT6835, MT6853, MT6855, MT6873, MT6877, MT6879, MT6883, MT6885, MT6886, MT6889, MT6893, MT6895, MT6897, MT6983, MT6985, MT6989, MT8168, MT8188, MT8195, MT8673, MT8675
  • mediatek mt6739
  • mediatek mt6761
  • mediatek mt6765
  • mediatek mt6768
  • mediatek mt6779
  • mediatek mt6781
  • mediatek mt6785
  • mediatek mt6789
  • mediatek mt6833
  • mediatek mt6835
  • mediatek mt6853
  • mediatek mt6855
  • mediatek mt6873
  • mediatek mt6877
  • mediatek mt6879
  • mediatek mt6883
  • mediatek mt6885
  • mediatek mt6886
  • mediatek mt6889
  • mediatek mt6893
  • mediatek mt6895
  • mediatek mt6897
  • mediatek mt6983
  • mediatek mt6985
  • mediatek mt6989
  • mediatek mt8168
  • mediatek mt8188
  • mediatek mt8195
  • mediatek mt8673
  • mediatek mt8675
  • google android

Classification

Weakness
  • CWE-754 Improper Check for Unusual or Exceptional Conditions

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.