Security readout for executives and security teams
Plain-English summary
This vulnerability affects specific Unisoc chipsets running Android 10 through 12. A local actor with System-level execution could trigger an out-of-bounds read in hci_server, potentially causing denial of service. Sources do not provide CVSS scoring, confirmed exploitation, or detailed remediation steps.
Executive priority
Treat this as an asset-scoping and vendor-follow-up item, not an emergency based on current evidence. Urgency increases for fleets containing affected Unisoc devices without clear firmware support or update visibility.
Technical view
The flaw is a missing bounds check in hci_server that can cause an out-of-bounds read. The described impact is local denial of service, requiring System execution privileges. The affected scope is Unisoc-listed chipsets on Android 10, Android 11, and Android 12.
Likely exposure
Exposure is most likely on devices using the listed Unisoc chipsets and affected Android versions. Organizations should focus on mobile, embedded, or IoT assets where chipset and firmware provenance are known or can be verified.
Exploitation context
The source bundle does not show CISA KEV listing or other evidence of active exploitation. The issue is described as local and requires System execution privileges, which limits direct remote attack scenarios but may matter after prior compromise.
Researcher notes
Evidence is limited to the CVE record and Unisoc advisory reference. No CVSS vector, CWE, proof of exploitation, patch version, or detailed trigger conditions are provided in the supplied sources, so validation should avoid assumptions beyond chipset, OS version, and vendor status.
Mitigation direction
- Review Unisoc advisory and device OEM bulletins for available firmware updates.
- Inventory devices using affected Unisoc chipsets and Android 10, 11, or 12.
- Prioritize updates for managed devices with exposed Bluetooth or broad local attack risk.
- If no update is available, follow vendor guidance and reduce untrusted local access.
Validation and detection
- Confirm device chipset model against the affected Unisoc list.
- Confirm Android major version and firmware build from device management records.
- Check OEM or Unisoc security bulletins for CVE-2023-33904 remediation status.
- Monitor vulnerability management systems for vendor scoring or patch metadata updates.
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-33904 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.