Security readout for executives and security teams
Plain-English summary
CVE-2023-30920 is a missing permission check in Unisoc messaging service software. On affected Android devices, a local actor could access information without needing extra execution privileges. The public record does not provide CVSS severity, attack details, or a named patch.
Executive priority
Treat this as a device-fleet exposure question, not an internet-facing emergency. Prioritize inventory and vendor patch confirmation for Unisoc-based Android devices, especially where messaging data may be sensitive.
Technical view
The flaw is described as a missing permission check in the messaging service, causing local information disclosure. Affected platforms are listed Unisoc chipsets running Android 10 through Android 13. No CWE, CVSS vector, exploit method, or remediation details are provided in the supplied sources.
Likely exposure
Exposure is likely limited to devices using the listed Unisoc chipsets on Android 10, 11, 12, or 13. Asset teams should identify OEM devices containing these SoCs, because end-user product names are not listed in the CVE bundle.
Exploitation context
The sources do not show active exploitation, and the CVE is not listed as KEV. The described attacker position is local, with no additional execution privileges needed. Public evidence is insufficient to assess exploit maturity or real-world targeting.
Researcher notes
The public data is sparse: no CVSS, CWE, patch identifier, vulnerable code path, or proof-of-concept details are provided. Analysis should stay anchored to local information disclosure via missing permission enforcement in the messaging service.
Mitigation direction
- Check Unisoc and OEM security guidance for firmware updates or advisories.
- Apply available OEM security updates to affected Android devices.
- Prioritize unsupported affected devices for replacement or isolation.
- Limit sensitive workloads on devices until patch status is confirmed.
Validation and detection
- Inventory Android devices by chipset, OEM model, and Android version.
- Map devices to the Unisoc affected chipset list.
- Check firmware and security patch levels against vendor guidance.
- Record devices with unknown chipset or patch status for follow-up.
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.
CVE-2023-30920 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
- CVE List V5 sourceCVE List V5
- https://www.unisoc.com/en_us/secy/announcementDetail/1676902764208259073CVE reference
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.