Security readout for executives and security teams
Plain-English summary
This CVE describes a missing permission check in a UNISOC Android messaging service. A local actor could potentially read information they should not access. The public record does not provide severity scoring, patch version details, or evidence of active exploitation.
Executive priority
Treat this as an inventory-and-patch management issue until vendor details clarify severity. It is not currently supported as internet-exploited or actively exploited, but affected mobile devices handling sensitive messages should be prioritized for firmware updates.
Technical view
UNISOC reports a missing permission check in a messaging service affecting listed chipsets on Android 10-13. The stated impact is local information disclosure with no additional execution privileges needed. Public sources do not provide CVSS, CWE mapping, vulnerable API details, patch level, or exploit mechanics.
Likely exposure
Exposure appears limited to Android devices using the listed UNISOC chipsets and affected Android 10-13 messaging service builds. Enterprise exposure depends on device inventory, OEM firmware lineage, and whether impacted models remain deployed.
Exploitation context
The source bundle does not show CISA KEV listing or cited evidence of active exploitation. The vulnerability is described as local information disclosure, so risk is most relevant where an attacker already has local device access or app-level interaction.
Researcher notes
The public record is sparse: no CVSS, CWE, patch build, proof-of-concept status, or technical root-cause detail is provided. Avoid assuming exploitability beyond local information disclosure from a missing permission check in the messaging service.
Mitigation direction
- Check UNISOC and OEM security advisories for fixed firmware.
- Prioritize OTA updates for affected UNISOC-based Android devices.
- Inventory deployed devices by chipset, model, Android version, and patch level.
- Limit use of unsupported or unpatched affected devices for sensitive messaging.
- Apply mobile device management controls where updates are unavailable.
Validation and detection
- Confirm whether deployed devices use listed UNISOC chipsets.
- Map each device model to OEM firmware and Android patch level.
- Review vendor advisory status for CVE-2023-30923 remediation details.
- Verify affected devices have received applicable OEM security updates.
- Document any devices without available fixes for risk acceptance or replacement.
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-30923 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.