Security readout for executives and security teams
Plain-English summary
This vulnerability is a missing permission check in a Unisoc Android telephony service. A local user or app could obtain information without needing extra execution privileges. Public sources do not provide CVSS, CWE, patch identifiers, or evidence of active exploitation.
Executive priority
Track this as a moderate fleet governance issue where Unisoc-based Android devices are present. It is not currently supported as an emergency from the provided sources because there is no KEV listing, no CVSS score, and no active exploitation evidence.
Technical view
CVE-2023-33883 affects listed Unisoc chipsets running Android 10 through Android 13. The flaw is described as a telephony service authorization failure causing local information disclosure. The record does not identify exposed data types, attack prerequisites beyond local access, or fixed firmware versions.
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. Organizations without Unisoc-based Android devices are unlikely to be affected based on the provided record.
Exploitation context
The source bundle states this is not in KEV and provides no cited evidence of active exploitation. The vulnerability is local, not remotely exploitable based on the supplied description. Public evidence is too limited to assess exploit maturity.
Researcher notes
The public record is sparse. It lacks CWE, CVSS, fixed build identifiers, affected telephony APIs, and data impact specifics. Analysis should stay limited to listed chipsets and Android versions unless vendor advisories provide broader scope.
Mitigation direction
- Check Unisoc and device OEM advisories for fixed firmware availability.
- Apply OEM or carrier Android firmware updates for affected device models.
- Prioritize managed fleets containing listed Unisoc chipsets and Android 10-13.
- Limit use of unsupported affected devices in sensitive environments.
- Request vendor confirmation where firmware lineage is unclear.
Validation and detection
- Inventory Android devices for the listed Unisoc chipsets.
- Confirm affected devices are running Android 10, 11, 12, or 13.
- Map device model firmware to Unisoc or OEM advisory status.
- Check whether affected models still receive security updates.
- Document devices requiring vendor confirmation 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-33883 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.