Security readout for executives and security teams
Plain-English summary
CVE-2023-52379 is a Huawei calendarProvider permission-control flaw that could expose confidential service data. The public record rates it high because exploitation requires no privileges or user interaction, but available sources do not explain the exact data exposed or attack path.
Executive priority
High priority for organizations using affected Huawei devices with sensitive business data. Focus on rapid inventory and vendor-guided update validation. Current sources support confidentiality risk, not an active compromise finding.
Technical view
The issue is classified as CWE-276 in Huawei HarmonyOS and EMUI calendarProvider. CVSS 3.1 is 7.5 with network access, low complexity, no privileges, no user interaction, high confidentiality impact, and no stated integrity or availability impact.
Likely exposure
Exposure is limited to the listed Huawei platforms: HarmonyOS 4.0.0, 3.1.0, 3.0.0, 2.1.0, 2.0.0 and EMUI 13.0.0, 12.0.0. Other products are not identified in the provided sources.
Exploitation context
The source bundle does not identify active exploitation, public exploit availability, or CISA KEV listing. Treat exploitation status as unconfirmed. The CVSS vector indicates remote, unauthenticated exploitability, but the public details are sparse.
Researcher notes
Public technical detail is limited to permission control in calendarProvider and confidentiality impact. Avoid assuming affected data types beyond service confidentiality. Use vendor bulletins and device patch metadata for validation rather than inferred exploit behavior.
Mitigation direction
- Review Huawei February 2024 security bulletin for official remediation details.
- Update affected HarmonyOS and EMUI devices according to Huawei guidance.
- Prioritize business-managed devices containing sensitive calendar or service data.
- Monitor Huawei advisories for corrected builds and follow-up notes.
Validation and detection
- Inventory Huawei device models and OS versions in the environment.
- Confirm no devices remain on the listed affected HarmonyOS or EMUI versions.
- Verify applied security updates against Huawei February 2024 bulletin guidance.
- Check MDM or endpoint records for patch compliance evidence.
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-276: 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-52379 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
- High
- CVSS
- 7.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N3.93.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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.
Incorrect Default Permissions
Incorrect Default Permissions represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.