Security readout for executives and security teams
Plain-English summary
CVE-2023-33893 is a missing permission check in UNISOC's fastDial service. The reported impact is local information disclosure without additional execution privileges. The public bundle does not provide CVSS scoring, CWE mapping, exploit details, or a named patch, so urgency depends on whether affected UNISOC-based Android devices are in use.
Executive priority
Treat this as an inventory and vendor-follow-up item unless affected UNISOC Android devices are confirmed in sensitive environments. The public evidence supports local information disclosure risk, but not confirmed exploitation or severity scoring.
Technical view
The issue affects fastDial service on listed UNISOC platforms running Android 10 through Android 13. A local actor may access information because a required permission check is missing. The source data identifies information disclosure only and does not describe the data exposed, attack path, or remediation state.
Likely exposure
Exposure is most likely on phones, tablets, IoT, or embedded Android devices using the listed UNISOC chipsets and Android 10, 11, 12, or 13. Risk depends on OEM firmware integration and patch status.
Exploitation context
The source bundle does not indicate active exploitation, and the CVE is not listed as KEV. The described attack context is local information disclosure with no additional execution privileges needed. No public exploit status is provided.
Researcher notes
The bundle provides limited technical detail: no CVSS, CWE, proof of exploitation, exposed data type, or fix version. The affected product list repeats some chipsets; preserve the vendor wording and validate against OEM device mappings.
Mitigation direction
- Inventory Android devices using the listed UNISOC chipsets and versions.
- Check UNISOC and OEM advisories for CVE-2023-33893 update availability.
- Apply OEM firmware or security updates when the vendor identifies a fixed build.
- Restrict untrusted app installation on potentially affected devices.
- Request patch status from the OEM if public guidance is incomplete.
Validation and detection
- Map device models to UNISOC chipset and Android version.
- Review OEM security bulletins for CVE-2023-33893 references.
- Confirm whether deployed firmware includes the vendor's security update.
- Document devices with unknown chipset or patch status for follow-up.
- Track any later CVSS, CWE, or exploitation updates from official sources.
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-33893 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.