Analyst readout for executives and security teams
Plain-English summary
CVE-2023-30936 is a Unisoc telephony service flaw where a missing permission check could expose information locally. Business risk is concentrated in Android devices using listed Unisoc chipsets on Android 10 through 13. The public record does not provide CVSS scoring, affected firmware builds, or a named fixed version.
Executive priority
Treat this as a targeted mobile fleet hygiene issue, not an internet-wide emergency. Prioritize inventory and OEM update checks for Unisoc-based Android devices, especially where mobile devices handle sensitive communications or regulated data.
Technical view
The issue is described as a missing permission check in the telephony service, leading to local information disclosure without additional execution privileges. Affected products listed are multiple Unisoc chipsets across Android 10, 11, 12, and 13. No CWE, CVSS vector, exploit details, or concrete patch version is provided in the supplied sources.
Likely exposure
Organizations may be exposed through managed or unmanaged Android devices using the listed Unisoc chipsets and Android 10-13 firmware. Exposure depends on OEM firmware lineage, update status, and whether the device includes the vulnerable telephony service implementation.
Exploitation context
The source bundle does not show active exploitation, and the CVE is not marked in KEV. The described access is local, so risk likely depends on local device access or an already-installed app context. No weaponized exploit or exploitation method is cited.
Researcher notes
Evidence is sparse. The public description identifies the vulnerable component and impact class but omits CVSS, CWE, affected firmware ranges, patch identifiers, and exploitability details. Do not infer broader Android or non-Unisoc impact from this bundle.
Mitigation direction
- Inventory Android devices for listed Unisoc chipsets and Android versions.
- Check Unisoc and device OEM advisories for firmware updates or fixed builds.
- Apply available OEM security updates through managed update channels.
- Restrict installation of untrusted apps on affected mobile fleets.
- Prioritize replacement or isolation for unsupported affected devices.
Validation and detection
- Confirm device chipset models against the affected Unisoc list.
- Record Android version and vendor security patch level for each device.
- Compare firmware builds against OEM or Unisoc remediation guidance.
- Use MDM reporting to identify unsupported or stale devices.
- Monitor CISA KEV and vendor advisories for exploitation updates.
Public sources used
Based on public source material and reviewed before publication.
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-30936 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.