Security readout for executives and security teams
Plain-English summary
This is a critical BootROM flaw in listed Unisoc chipsets. A missing RSA key size check during Certificate Type 0 validation can cause memory corruption. Because BootROM code sits very early in device startup, exposure is mainly tied to devices using the affected SoCs and the vendor/OEM secure-boot implementation.
Executive priority
Treat this as high priority for asset identification and supplier follow-up. The business risk is strongest where affected Unisoc-based devices handle sensitive data, physical access control, field operations, or regulated workloads.
Technical view
CVE-2022-38692 is CWE-119 in Unisoc BootROM Certificate Type 0 validation. The CVE states missing size checking for RSA keys may lead to a memory buffer overflow without extra execution privileges. CVSS is 9.8, with no privileges or user interaction required. Public sources do not name fixed firmware or practical exploitation status.
Likely exposure
Organizations may be exposed through phones, tablets, IoT, or embedded products using Unisoc SC9863A, T310, T606, T610, T612, T616, T618, T760, T770, T820, or S8000 SoCs.
Exploitation context
The source bundle does not show CISA KEV listing or confirmed active exploitation. The issue is high-impact because it affects BootROM validation, but practical exploitability and delivery conditions are not fully evidenced in the provided sources.
Researcher notes
Evidence is limited to the CVE record and NCC Group reference. Do not assume patched versions, affected device models, exploit availability, or active exploitation beyond those sources. Focus validation on chipset mapping, OEM firmware status, and boot-chain exposure.
Mitigation direction
- Inventory products and suppliers using the listed Unisoc SoCs.
- Check Unisoc and device OEM advisories for firmware or lifecycle guidance.
- Prioritize affected devices used in sensitive, managed, or exposed environments.
- Apply vendor-approved firmware updates when available.
- Retire or isolate devices when no vendor remediation path exists.
Validation and detection
- Map device models to underlying Unisoc chipset identifiers.
- Compare firmware versions against vendor or OEM security bulletins.
- Ask suppliers whether Certificate Type 0 BootROM validation is exposed.
- Review mobile/IoT asset management records for affected SoCs.
- Track CVE and NCC Group references for remediation 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.
CWE-119: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2022-38692 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
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Source materials
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.
Improper Restriction of Operations within the Bounds of a Memory Buffer
Improper Restriction of Operations within the Bounds of a Memory Buffer represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.