Security readout for executives and security teams
Plain-English summary
CVE-2023-30927 is a Unisoc Android telephony-service issue where a missing permission check may expose local information. It affects listed Unisoc chipsets on Android 10 through Android 13. Public sources do not provide a CVSS score, CWE, fixed build, or detailed patch status.
Executive priority
Treat this as a targeted mobile-fleet hygiene issue rather than an internet-facing emergency. Prioritize organizations with large deployments of low-cost or embedded Android devices using Unisoc chipsets, especially where telephony metadata or device information sensitivity matters.
Technical view
The vulnerability is described as a missing permission check in the telephony service, leading to local information disclosure without additional execution privileges. The affected list covers multiple Unisoc SoCs, including SC9863A, SC9832E, SC7731E, T310, T606, T610, T612, T616, T618, T760, T770, T820, and S8000 on Android 10-13.
Likely exposure
Exposure is most likely on Android devices using the listed Unisoc chipsets and vendor firmware based on Android 10, 11, 12, or 13. The source bundle does not identify specific OEM device models, carrier builds, or fixed firmware versions.
Exploitation context
The cited description supports local information disclosure, not remote exploitation. The CVE is not listed as KEV in the provided bundle, and no cited source states active exploitation. Public details are too limited to assess exploit maturity or practical attack prerequisites beyond local access context.
Researcher notes
Public evidence is sparse. The issue appears to be an Android telephony permission-boundary flaw in Unisoc platform code. The sources do not provide CVSS, CWE, patch identifiers, proof-of-concept status, affected OEM models, or enough detail to design a source-level verification without vendor firmware context.
Mitigation direction
- Check Unisoc advisory and OEM bulletins for fixed firmware covering the listed chipsets.
- Prioritize updates for Android 10-13 devices using affected Unisoc SoCs.
- Ask device vendors for fixed build identifiers if advisories are incomplete.
- Limit sensitive telephony data exposure on unmanaged or unpatched devices where possible.
Validation and detection
- Inventory Android devices by chipset, OEM firmware build, and Android version.
- Map devices to the affected Unisoc SoC list in the CVE record.
- Confirm whether OEM firmware includes a fix for CVE-2023-30927.
- Review mobile-device telemetry for untrusted local apps on affected devices.
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-30927 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.