Security readout for executives and security teams
Plain-English summary
CVE-2023-33890 is a missing permission check in a UNISOC telephony service. It may let a local actor disclose information without needing extra execution privileges. The public record does not provide CVSS scoring, exploit details, or confirmed active exploitation.
Executive priority
Treat this as a targeted mobile-device exposure, not an internet-facing emergency. Prioritize inventory and OEM update verification for fleets using affected UNISOC-based Android devices, especially where devices handle sensitive communications or personal data.
Technical view
The issue affects listed UNISOC chipsets on Android 10, 11, 12, and 13. The vulnerable component is described only as telephony service. The impact is local information disclosure caused by absent permission enforcement. Public sources do not define the exposed data, attack prerequisites beyond local access, or patch level.
Likely exposure
Exposure is most likely in Android devices using the listed UNISOC platforms, including SC9863A, SC9832E, SC7731E, T-series, T820, and S8000 chipsets, on Android 10 through Android 13.
Exploitation context
CISA KEV status is false in the supplied data, and no cited source claims exploitation in the wild. The available description supports local information disclosure only; remote exploitation is not evidenced.
Researcher notes
The public record is sparse: no CVSS vector, CWE, patch identifier, vulnerable API, or data class is provided. Analysis should stay close to vendor and CVE text unless additional primary technical detail becomes available.
Mitigation direction
- Check UNISOC and device OEM advisories for firmware or Android security updates.
- Inventory Android devices using the listed UNISOC chipsets and Android versions.
- Prioritize supported device updates through normal mobile device management processes.
- Limit installation of untrusted local apps on potentially affected devices.
- Retire or isolate devices that cannot receive OEM security updates.
Validation and detection
- Confirm device chipset and Android version through asset inventory or OEM documentation.
- Compare firmware build levels against UNISOC and OEM security guidance.
- Review whether affected devices remain in production or sensitive-user groups.
- Check vulnerability scanners or MDM inventory for matching hardware and OS versions.
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-33890 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.