Security readout for executives and security teams
Plain-English summary
This vulnerability affects certain Android devices using Unisoc chipsets. A missing permission check in the telephony service could let a local actor access information they should not see. The public sources do not state what information is exposed or provide a severity score.
Executive priority
Prioritize this for asset identification and vendor update tracking, especially in managed Android fleets. Business urgency is uncertain because severity and exploitation evidence are not provided, but unsupported affected devices can create avoidable privacy and compliance risk.
Technical view
CVE-2023-33900 is a local information disclosure issue in a Unisoc telephony service caused by a missing permission check. No additional execution privileges are required. Sources list affected chipsets and Android 10 through 13, but do not provide CVSS, CWE, exact data exposure, or patch-version detail.
Likely exposure
Exposure is most likely in Android device fleets using the listed Unisoc chipsets on Android 10, 11, 12, or 13. This may include budget handsets, managed mobile fleets, shared devices, and embedded Android deployments. The sources describe local exposure, not remote network exposure.
Exploitation context
The provided sources do not report active exploitation, public exploit availability, or CISA KEV listing. Treat this as a local information disclosure risk until vendor or OEM guidance gives stronger severity or exploitation evidence.
Researcher notes
Key unknowns are the protected telephony interface, exposed data type, vulnerable code path, and fixed firmware baseline. The CVE record confirms local information disclosure from a missing permission check, but the source bundle does not support exploitability claims beyond that.
Mitigation direction
- Inventory Android devices for the listed Unisoc chipsets and Android 10 through 13.
- Check Unisoc and device OEM advisories for firmware or security updates.
- Apply OEM-provided Android firmware updates when available.
- Limit installation of untrusted local apps on affected managed devices.
- Retire or isolate devices where OEM support cannot be confirmed.
Validation and detection
- Confirm whether devices use any listed Unisoc chipset.
- Check Android version and OEM security patch level for affected devices.
- Review MDM inventory for unmanaged or sideload-capable affected devices.
- Compare findings against Unisoc and OEM advisory details.
- Document unsupported devices requiring risk acceptance 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-33900 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.