Security readout for executives and security teams
Plain-English summary
This CVE describes a flaw in Unisoc Android telephony service code that could let a local actor disclose information without needing extra privileges. The sources do not provide CVSS, affected firmware builds, exploit details, or a named patch level.
Executive priority
Treat this as a targeted asset-identification and patch-status task, not an emergency response, unless your fleet includes sensitive Unisoc-based Android devices or new exploitation evidence appears.
Technical view
CVE-2023-33886 is a missing permission check in the telephony service affecting listed Unisoc chipsets running Android 10 through Android 13. The stated impact is local information disclosure with no additional execution privileges required. The available bundle does not identify the exposed data, attack preconditions beyond local access, or fixed versions.
Likely exposure
Exposure is most likely on Android devices using the listed Unisoc chipsets and Android 10, 11, 12, or 13. Business exposure depends on OEM firmware lineage and whether vendor security updates were applied.
Exploitation context
The provided sources do not show active exploitation, and the CVE is not marked as CISA KEV. The issue is local, so risk is tied to device access, installed apps, and endpoint control maturity.
Researcher notes
Public detail is sparse: no CVSS vector, CWE, patch version, or exploit status is included. Analysis should stay constrained to the stated telephony permission-check flaw and local information disclosure impact.
Mitigation direction
- Inventory Android devices using listed Unisoc chipsets and Android versions.
- Check Unisoc and OEM advisories for fixed firmware or security updates.
- Apply available OEM firmware and Android security updates through managed deployment.
- Limit installation of untrusted apps on potentially affected devices.
- Prioritize managed or high-sensitivity devices for vendor status checks.
Validation and detection
- Confirm device chipset, Android version, and OEM firmware build.
- Compare installed firmware against Unisoc and OEM security guidance.
- Check mobile device management records for update compliance.
- Review app installation controls on affected device groups.
- Track vendor advisories for patch identifiers or mitigation updates.
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-33886 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.