Security readout for executives and security teams
Plain-English summary
CVE-2023-33888 is a Unisoc telephony service permission-check flaw. A local user or app context could disclose information without needing extra privileges. The public record does not provide CVSS, detailed impact, or confirmed exploitation, so urgency depends on whether your Android device fleet uses the listed Unisoc chipsets.
Executive priority
Treat this as an exposure-identification item until vendor remediation status is confirmed. It is not currently supported as actively exploited, but telephony information disclosure can matter for regulated or privacy-sensitive mobile fleets.
Technical view
The issue is a missing permission check in the telephony service affecting listed Unisoc chipsets on Android 10 through Android 13. The stated impact is local information disclosure with no additional execution privileges needed. Public sources do not provide CWE, CVSS, affected device models, or exploit details.
Likely exposure
Exposure is most likely in Android devices using the listed Unisoc SC9863A, SC9832E, SC7731E, T-series, T820, or S8000 chipsets on Android 10-13. The sources do not identify specific handset models or OEM firmware status.
Exploitation context
The CVE is not listed as CISA KEV in the provided bundle, and no cited source states active exploitation. The known attack context is local information disclosure; remote exploitation is not supported by the provided evidence.
Researcher notes
Public detail is sparse. The record identifies a telephony service missing permission check and local information disclosure only. No CVSS, CWE, patch version, device model mapping, proof of concept, or exploit status is provided in the bundle.
Mitigation direction
- Check Unisoc and OEM advisories for firmware guidance.
- Inventory Android devices using the listed Unisoc chipsets.
- Prioritize managed devices handling sensitive calls, SMS, or subscriber data.
- Apply vendor or carrier firmware updates when available.
- Monitor CVE and vendor records for severity or fix updates.
Validation and detection
- Confirm whether fleet devices use affected Unisoc chipsets.
- Check Android versions against the listed Android 10-13 range.
- Review OEM security bulletins for CVE-2023-33888 coverage.
- Verify firmware update status through MDM or asset tooling.
- Document devices lacking vendor remediation guidance.
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-33888 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.
