Security readout for executives and security teams
Plain-English summary
This CVE describes a missing permission check in a UNISOC telephony service. A local app or user path could access information that should have required permission. The public record does not provide CVSS scoring, impacted data details, or confirmed fixed firmware versions.
Executive priority
Treat this as an inventory and vendor-follow-up item, not an emergency based on current evidence. Priority rises for fleets with UNISOC-based Android devices handling sensitive communications or regulated data, especially where app installation is loosely controlled.
Technical view
CVE-2023-30934 affects listed UNISOC chipsets running Android 10 through Android 13. The flaw is in the telephony service and is characterized as local information disclosure with no additional execution privileges required. The source bundle does not include CWE mapping, CVSS metrics, exploit detail, or patch version identifiers.
Likely exposure
Exposure is most relevant to Android devices using the listed UNISOC chipsets and Android 10, 11, 12, or 13. Organizations should verify actual device models and OEM firmware, because the CVE names chipsets and Android generations rather than end-user handset models.
Exploitation context
The source bundle does not show CISA KEV inclusion and does not cite active exploitation. The issue is local, so remote internet exposure is not indicated by the provided sources. Risk depends on whether an attacker can run code locally or otherwise interact with the affected telephony service.
Researcher notes
Public detail is sparse. The record identifies a telephony-service permission check failure and broad chipset and Android-version exposure, but lacks vulnerable code paths, affected APIs, fixed versions, CVSS, or CWE. Avoid assuming exploitation or specific data leakage beyond local information disclosure.
Mitigation direction
- Inventory Android devices using the listed UNISOC chipsets and Android versions.
- Check UNISOC and OEM firmware guidance for fixed builds or security updates.
- Apply OEM-approved updates when available through normal mobile device channels.
- Limit installation of untrusted local apps on potentially affected devices.
- Prioritize managed or sensitive-use devices for vendor verification.
Validation and detection
- Confirm device chipset, Android version, OEM build, and security patch level.
- Map each device model to the UNISOC affected chipset list.
- Review UNISOC and OEM advisories for matching remediation identifiers.
- Verify managed devices have received applicable OTA or firmware updates.
- Track exceptions where no vendor fix information 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-30934 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.