Security readout for executives and security teams
Plain-English summary
CVE-2023-32789 is a Unisoc Android telephony service issue where a missing permission check could let a local actor obtain information they should not access. The public data does not describe remote compromise, privilege escalation, or active exploitation.
Executive priority
Treat this as a targeted device-fleet hygiene issue. Prioritize environments with Unisoc-based Android devices handling sensitive communications or deployed at scale.
Technical view
The flaw is described as a missing permission check in the telephony service, causing local information disclosure without additional execution privileges. Affected entries list multiple Unisoc chipsets running Android 10, 11, 12, or 13. CVSS and CWE details are not provided in the source bundle.
Likely exposure
Exposure is most likely in Android devices or embedded products using the listed Unisoc chipsets and Android 10 through Android 13 firmware. OEM-specific firmware status must be verified.
Exploitation context
The source bundle does not show CISA KEV listing or cited evidence of public exploitation. The described attack context is local information disclosure, not remote exploitation.
Researcher notes
The public record lacks CVSS, CWE, detailed affected firmware build ranges, and explicit fix details. Validate exposure at OEM firmware level because chipset listings alone may not map cleanly to deployed products.
Mitigation direction
- Review the Unisoc advisory and relevant OEM bulletins for fixed firmware guidance.
- Deploy vendor or OEM security updates where available for affected device models.
- Inventory Android devices using the listed Unisoc chipsets and Android versions.
- Restrict installation of untrusted local apps on potentially affected devices.
- Retire or isolate devices without a supported firmware update path.
Validation and detection
- Identify device models and chipsets across mobile and embedded fleets.
- Confirm whether devices run Android 10, 11, 12, or 13 firmware.
- Compare firmware builds against Unisoc and OEM security guidance.
- Check MDM records for affected devices lacking current security updates.
- Document unresolved devices requiring compensating controls or replacement.
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-32789 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.