Skip to content
Fencer Vulns
high 7.5

CVE-2023-32845 json

In 5G Modem, there is a possible system crash due to improper error handling.

published 2023-12-04 2 y ago modified 2026-06-17 4 mo ago also EUVD-2023-37066

cvss
7.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.4%
EPSS 1.4% chance of exploitation in 30 days, percentile 72%
public exploits
0
none known

Summary

In 5G Modem, there is a possible system crash due to improper error handling. This could lead to remote denial of service when receiving malformed RRC messages, with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: MOLY01128524; Issue ID: MOLY01139296 (MSV-860).

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
2 y ago

Exploit prediction

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

CVSS scores

assigned by version score vector
NVD 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected products

  • MediaTek, Inc. MT2735, MT2737, MT6297, MT6298, MT6813, MT6815, MT6833, MT6835, MT6853, MT6855, MT6873, MT6875, MT6875T, MT6877, MT6879, MT6880, MT6883, MT6885, MT6886, MT6889, MT6890, MT6891, MT6893, MT6895, MT6895T, MT6896, MT6897, MT6980, MT6980D, MT6983, MT6985, MT6989, MT6990
  • mediatek mt2735
  • mediatek mt2737
  • mediatek mt6297
  • mediatek mt6298
  • mediatek mt6813
  • mediatek mt6815
  • mediatek mt6833
  • mediatek mt6835
  • mediatek mt6853
  • mediatek mt6855
  • mediatek mt6873
  • mediatek mt6875
  • mediatek mt6875t
  • mediatek mt6877
  • mediatek mt6879
  • mediatek mt6880
  • mediatek mt6883
  • mediatek mt6885
  • mediatek mt6886
  • mediatek mt6889
  • mediatek mt6890
  • mediatek mt6891
  • mediatek mt6893
  • mediatek mt6895
  • mediatek mt6895t
  • mediatek mt6896
  • mediatek mt6897
  • mediatek mt6980
  • mediatek mt6980d
  • mediatek mt6983
  • mediatek mt6985
  • mediatek mt6989
  • mediatek mt6990

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.