LiveActive security incident?Get immediate response
CVE Record

CVE-2022-38696: In BootRom, there's a possible missing payload size check.

In BootRom, there's a possible missing payload size check. This could lead to memory buffer overflow without requiring additional execution privileges.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2022-38696 is a critical Unisoc BootRom memory corruption issue. A missing payload size check could allow a buffer overflow without privileges, potentially affecting confidentiality, integrity, and availability. The provided sources do not identify active exploitation or a named patch.

Executive priority

Treat this as high-priority asset exposure work, especially for fleets containing Unisoc-based devices. The technical impact is severe, but remediation confidence depends on vendor confirmation because the provided sources do not name a fix.

Technical view

The CVE describes CWE-119 in BootRom: insufficient payload size validation may cause memory buffer overflow. The affected entry names multiple Unisoc chipsets and CVSS 3.1 scores it 9.8 with no privileges or user interaction required. No exploit details, mitigations, or fixed versions are provided in the bundle.

Likely exposure

Exposure is most likely in phones, IoT, or embedded devices using the listed Unisoc chipsets: SC9863A, T310, T610, T618, T606, T612, T616, T760, T770, T820, S8000, T750, or T765.

Exploitation context

The CVE is not listed as KEV in the supplied bundle, so active exploitation is not evidenced here. NCC Group research is referenced, but this bundle does not provide exploit status, public exploit availability, or attack prerequisites beyond the CVSS vector.

Researcher notes

Do not assume affected consumer device models from chipset names alone. The useful next step is exposure confirmation and vendor advisory review. The BootRom location suggests low-level boot-chain relevance, but patchability and practical attack paths are not established in the supplied evidence.

Mitigation direction

  • Inventory devices and embedded products using the affected Unisoc chipsets.
  • Request vendor or Unisoc guidance for firmware, boot-chain, or hardware remediation options.
  • Prioritize replacement planning where vendors cannot provide remediation.
  • Restrict exposure of device management, flashing, or recovery interfaces where operationally possible.

Validation and detection

  • Map device models to chipsets using procurement records, MDM, SBOMs, or vendor attestations.
  • Check vendor advisories for CVE-2022-38696 and listed Unisoc chipsets.
  • Confirm whether affected devices have firmware or platform updates available.
  • Document unsupported or unverifiable devices as residual risk.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · low confidence lookup

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 lookup
cve · low confidence lookup

CVE-2022-38696 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
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

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2022-38696Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Unisoc (Shanghai) Technologies Co., Ltd.SC9863A/T310/T610/T618/T606/T612/T616/T760/T770/T820/S8000/T750/T765/unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-119 · source CWE mapping

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.