Security readout for executives and security teams
Plain-English summary
CVE-2023-30918 is a local information disclosure issue in Unisoc telephony service code. A missing permission check could let a local actor or app access information it should not receive. Public sources do not provide business-impact details, data types exposed, or a CVSS score.
Executive priority
Treat this as an exposure-discovery item rather than an emergency unless affected Unisoc-based Android devices handle sensitive data. The current public evidence lacks severity scoring, exploit confirmation, and remediation specifics, so priority should be driven by device criticality and update availability.
Technical view
The CVE describes a missing permission check in the telephony service affecting listed Unisoc chipsets running Android 10 through Android 13. The stated impact is local information disclosure with no additional execution privileges needed. The source bundle does not identify a CWE, CVSS vector, patch level, or exploit prerequisites beyond local access.
Likely exposure
Exposure is most likely on Android devices using the listed Unisoc chipsets: SC9863A, SC9832E, SC7731E, T310, T606, T610, T612, T616, T618, T760, T770, T820, and S8000 on Android 10-13.
Exploitation context
The CVE is not listed as KEV in the provided bundle, and the cited sources do not state active exploitation. The issue is local, so risk depends on affected device presence, app installation controls, and whether vendor or OEM firmware updates exist.
Researcher notes
Public detail is sparse. The record names telephony service, missing permission check, local information disclosure, and affected Unisoc chipsets with Android 10-13. It does not disclose affected APIs, data exposed, proof of exploitation, CVSS, CWE, or exact patched versions.
Mitigation direction
- Inventory Android devices using the listed Unisoc chipsets and Android versions.
- Check Unisoc and device OEM guidance for fixed firmware or security update availability.
- Apply vendor-provided Android firmware updates when available through managed update channels.
- Limit installation of untrusted local apps on potentially affected devices.
- Prioritize managed or high-sensitivity devices for review first.
Validation and detection
- Confirm device chipset and Android version through MDM, asset records, or vendor documentation.
- Compare current firmware and Android security patch level with OEM remediation guidance.
- Review fleet inventory for unmanaged affected devices outside standard update channels.
- Document devices where no vendor fix or update path is available.
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-30918 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.