Security readout for executives and security teams
This is a low-severity Zephyr RTOS Bluetooth issue where inconsistent length handling over the SPI HCI interface can cause limited confidentiality, integrity, and availability impact. The CVSS vector requires physical access, high attack complexity, and user interaction, so business urgency is generally low unless exposed devices are safety-critical or difficult to update. Exposure is most likely in embedded or IoT products using Zephyr RTOS with Bluetooth HCI transported over SPI. Systems not using Zephyr, Bluetooth, or this HCI-over-SPI path are not evidenced as affected by the provided sources. Treat this as a low-priority vulnerability unless the affected devices are widely deployed, physically accessible, safety-sensitive, or hard to patch. The key management task is asset identification and vendor-guided firmware remediation, not emergency response. Mitigation focus: Identify products or firmware builds using affected Zephyr versions.; Check the Zephyr GitHub advisory for vendor-confirmed remediation.; Update Zephyr or device firmware when vendor guidance provides a fixed release..
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-130: 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-2020-10065 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
- Low
- CVSS
- 3.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:P/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L
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:P/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L0.43.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
3.8LowVector: CVSS:3.1/AV:P/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L
Source materials
- CVE List V5 sourceCVE List V5
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 Handling of Length Parameter Inconsistency
Improper Handling of Length Parameter Inconsistency represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.