Security readout for executives and security teams
Plain-English summary
This vulnerability is a missing permission check in a Unisoc telephony service. A local actor could access information they should not be able to see, without needing additional execution privileges. The public bundle does not provide CVSS, exploit detail, or a confirmed patch.
Executive priority
Treat this as a targeted mobile fleet exposure review, not an emergency based on current evidence. Prioritize organizations with Unisoc-based Android devices, especially where devices handle sensitive communications or permit unmanaged app installation.
Technical view
CVE-2023-30940 affects listed Unisoc chipsets running Android 10 through Android 13. The issue is in telephony service authorization: a missing permission check may allow local information disclosure. The sources do not identify the exposed data, attack prerequisites beyond local access, or remediation specifics.
Likely exposure
Exposure is most likely on Android devices using the listed Unisoc chipsets and Android 10, 11, 12, or 13 firmware. Organizations may need OEM or carrier firmware data to confirm whether deployed devices contain the affected telephony service build.
Exploitation context
The source bundle does not show CISA KEV listing or any cited evidence of active exploitation. The described impact is local information disclosure, not remote code execution. Practical risk depends on device fleet composition and whether untrusted local applications or users can interact with the telephony service.
Researcher notes
The public record is sparse: no CVSS vector, CWE, patch version, or detailed vulnerable interface is included in the provided bundle. Avoid assuming affected OEM models beyond the listed Unisoc platforms. Validation should focus on chipset and firmware confirmation through vendor channels.
Mitigation direction
- Check Unisoc and OEM advisories for confirmed remediation guidance.
- Inventory devices using the listed Unisoc chipsets and Android versions.
- Prioritize OEM or carrier firmware updates when available.
- Limit installation of untrusted applications on potentially affected devices.
- Track CVE updates for severity, patch, or exploitation changes.
Validation and detection
- Map mobile assets to chipset model and Android version.
- Compare device firmware status against Unisoc and OEM guidance.
- Confirm whether affected Unisoc chipsets exist in managed fleets.
- Review mobile management controls for app installation restrictions.
- Monitor CVE and vendor records for added technical details.
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-30940 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.