Security readout for executives and security teams
Plain-English summary
CVE-2023-30942 is a Unisoc telephony service issue where a missing permission check may let a local actor access information they should not see. The public record does not provide CVSS scoring, affected device models, or confirmed fixes beyond the referenced Unisoc advisory.
Executive priority
Treat as a targeted mobile fleet exposure item, not a confirmed emergency. Prioritize asset identification and vendor update tracking, especially for organizations using low-cost or embedded Android devices with Unisoc chipsets.
Technical view
The CVE describes local information disclosure in the telephony service due to a missing permission check. Listed affected Unisoc chipsets span Android 10 through Android 13. No CWE, CVSS vector, exploit details, or patch version is present in the provided bundle.
Likely exposure
Exposure is limited to devices using the named Unisoc chipsets and Android 10, 11, 12, or 13 telephony stack covered by the advisory.
Exploitation context
The record says local access is required and no additional execution privileges are needed. CISA KEV is false, and the bundle provides no evidence of active exploitation.
Researcher notes
The public bundle is sparse: no CVSS, CWE, patch identifier, or exploit evidence is provided. Analysis should stay anchored to local information disclosure from a telephony permission-check failure and avoid assuming specific leaked data types.
Mitigation direction
- Inventory Android devices using the listed Unisoc chipsets.
- Check Unisoc and OEM guidance for patched firmware or security updates.
- Prioritize managed devices that handle sensitive call, SIM, or subscriber data.
- Limit installation of untrusted local apps on potentially affected devices.
- Monitor vendor advisories for clarified patch and severity information.
Validation and detection
- Map device models to chipset and Android version.
- Compare deployed firmware against Unisoc or OEM advisory guidance.
- Confirm whether affected devices remain on Android 10 through Android 13 builds.
- Review MDM inventory for unmanaged or sideload-capable affected devices.
- Track whether vendor release notes mention this CVE.
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-30942 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.