Security readout for executives and security teams
Plain-English summary
CVE-2023-33882 is a UNISOC telephony service permission-check flaw. On affected Android devices, a local actor could disclose information without needing additional execution privileges. The public bundle does not provide CVSS, CWE, fixed versions, or confirmed active exploitation.
Executive priority
Treat this as a targeted device-fleet exposure issue, not a confirmed internet-scale emergency. Priority is moderate operational follow-up where UNISOC Android devices handle sensitive calls, identifiers, location-adjacent workflows, or regulated data.
Technical view
The issue is a missing permission check in the telephony service affecting listed UNISOC chipsets across Android 10 through Android 13. The documented impact is local information disclosure. The available record does not describe exposed data types, attack preconditions beyond local access, or remediation details.
Likely exposure
Exposure is likely limited to Android devices using the named UNISOC chipsets and affected Android versions. Organizations should map this to mobile, IoT, rugged, or embedded Android fleets supplied by OEMs using UNISOC silicon.
Exploitation context
The source bundle says local information disclosure is possible with no additional execution privileges needed. It does not cite public exploitation, weaponized proof of concept, or CISA KEV listing; active exploitation should not be assumed.
Researcher notes
The public record is sparse: no CVSS, CWE, fixed version, exploit detail, or data-type description is included. Keep analysis constrained to missing telephony permission enforcement and local information disclosure until vendor or OEM advisories provide more detail.
Mitigation direction
- Identify devices using affected UNISOC chipsets and Android 10 through 13.
- Check UNISOC and OEM firmware guidance for fixed builds or security updates.
- Apply vendor-approved Android security updates when available.
- Limit installation of untrusted local applications on affected devices.
- Prioritize managed or sensitive-use devices for remediation tracking.
Validation and detection
- Inventory device models, chipsets, Android versions, and security patch levels.
- Compare fleet data against the affected UNISOC product list.
- Review OEM release notes for CVE-2023-33882 coverage.
- Confirm updated firmware is deployed on affected device groups.
- Document devices where vendor fix status remains unknown.
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-33882 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.