Security readout for executives and security teams
Plain-English summary
CVE-2023-33889 is a missing permission check in a Unisoc Android telephony service. A local actor could obtain information without needing additional execution privileges. The public sources do not provide CVSS, detailed data types exposed, or patch instructions.
Executive priority
Treat this as an inventory-driven mobile exposure item. It does not show confirmed exploitation in the provided sources, but affected Android devices may need OEM firmware updates once available or verified.
Technical view
The issue affects listed Unisoc chipsets running Android 10, 11, 12, or 13. The weakness is described only as a telephony service missing permission check causing local information disclosure. No CWE, CVSS vector, exploit detail, or confirmed fix is provided in the source bundle.
Likely exposure
Exposure is most likely on Android devices using the named Unisoc chipsets and Android versions. Risk depends on device inventory, OEM firmware status, and whether updated vendor builds have addressed this issue.
Exploitation context
The CVE record indicates local information disclosure with no additional execution privileges required. It is not listed as CISA KEV in the bundle, and the provided sources do not claim active exploitation.
Researcher notes
Public detail is sparse. The source bundle does not identify the protected telephony operation, disclosed information, permission name, patch level, or reproducible validation method. Avoid assuming exploitability beyond local information disclosure.
Mitigation direction
- Identify Android devices using affected Unisoc chipsets.
- Check Unisoc and device OEM guidance for fixed firmware.
- Prioritize updates for shared, unmanaged, or high-sensitivity devices.
- Limit untrusted local app exposure where practical.
Validation and detection
- Map mobile inventory to the listed Unisoc chipsets and Android versions.
- Confirm current firmware build levels with OEM security bulletins.
- Check whether vendor advisories mention CVE-2023-33889 remediation.
- Document devices without available OEM update paths.
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-33889 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.