Security readout for executives and security teams
Plain-English summary
CVE-2023-37245 is a Huawei-reported buffer overflow in the modem pinctrl module. If exploited, it may affect modem integrity and availability, meaning modem behavior could be altered or disrupted. The source bundle does not provide CVSS scoring, technical depth, or confirmed exploitation.
Executive priority
Treat this as a targeted Huawei fleet update and validation issue. It is not supported as an emergency exploitation event by the supplied sources, but modem disruption can affect mobile connectivity, field operations, and device reliability.
Technical view
The vulnerability is mapped to CWE-120 and affects Huawei HarmonyOS 3.0.0, 2.0.0, 2.1.0 and EMUI 13.0.0, 12.0.0. Huawei describes impact to modem integrity and availability. No attack vector, privileges, fixed build, or exploit details are provided in the supplied sources.
Likely exposure
Exposure is most likely limited to Huawei devices running the listed HarmonyOS or EMUI versions. Confirm exact device models, build numbers, and bulletin applicability through Huawei guidance because the source bundle does not provide CPEs or fixed versions.
Exploitation context
CVE-2023-37245 is not listed as KEV in the source bundle. The provided sources do not cite active exploitation, public exploitation, or exploitation prerequisites. Treat exploitation evidence as incomplete rather than absent in the wider ecosystem.
Researcher notes
Key gaps are CVSS, attack vector, fixed versions, model mapping, and exploitability conditions. The safest source-grounded position is to validate affected Huawei OS versions and follow Huawei bulletin updates without assuming broader product exposure.
Mitigation direction
- Review Huawei July 2023 bulletin guidance for affected device builds.
- Apply official Huawei security updates where available for listed versions.
- Prioritize managed Huawei devices with modem-dependent business use.
- Use MDM reporting to identify outdated HarmonyOS and EMUI devices.
- Monitor Huawei advisories for fixed-build or model-specific clarification.
Validation and detection
- Inventory Huawei devices and record HarmonyOS or EMUI versions.
- Compare device builds against Huawei July 2023 bulletin entries.
- Confirm update installation through MDM or device-management records.
- Check support status for devices unable to receive updates.
- Track modem availability incidents on affected Huawei fleets.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-120: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2023-37245 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')
Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.