LiveActive security incident?Get immediate response
CVE Record

CVE-2020-10061: Error handling invalid packet sequence

Improper handling of the full-buffer case in the Zephyr Bluetooth implementation can result in memory corruption. This issue affects: zephyrproject-rtos zephyr version 2.2.0 and later versions, and version 1.14.0 and later versions.

HighCVSS 8.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This flaw is in Zephyr's Bluetooth implementation. Under a full-buffer error condition, invalid packet handling can corrupt memory, potentially affecting confidentiality, integrity, and availability on devices using affected Zephyr versions.

Executive priority

Prioritize affected Bluetooth-enabled products, especially deployed devices where firmware updates are slow. The issue is high severity, but the provided evidence does not support claims of active exploitation.

Technical view

CVE-2020-10061 is a CWE-119 memory corruption issue caused by improper handling of the full-buffer case in Zephyr Bluetooth packet processing. The CVSS 3.1 score is 8.1 with local attack vector, high complexity, no privileges, no user interaction, and scope change.

Likely exposure

Exposure is most likely in embedded, IoT, or product firmware using Zephyr Bluetooth from the affected version lines named by the CVE source. Internet-facing exposure is not indicated by the provided evidence.

Exploitation context

The source bundle does not show CISA KEV listing or public active exploitation evidence. Exploitation is rated local and high-complexity by CVSS, so physical or nearby access may matter more than network perimeter exposure.

Researcher notes

Key gaps are fixed-version details, exploitability constraints beyond CVSS, and product-specific exposure. Focus analysis on Zephyr Bluetooth buffer handling, affected branches, and whether downstream vendors incorporated the referenced fixes.

Mitigation direction

  • Inventory products and firmware that include Zephyr Bluetooth.
  • Compare embedded Zephyr versions against the vendor advisory.
  • Review Zephyr PRs and advisory for the vendor-supported fixed release.
  • Update affected firmware through normal product release channels.
  • If updates are unavailable, check Zephyr guidance for supported mitigations.

Validation and detection

  • Confirm whether Bluetooth support is compiled into the firmware.
  • Record the Zephyr version and branch used in each shipped build.
  • Review SBOMs, build manifests, or source dependencies for Zephyr references.
  • Test only in authorized lab conditions using vendor-safe regression cases.
  • Track remediation evidence by product, firmware version, and deployment status.
Prepared
Confidence
medium
Sources
8

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-2020-10061 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
High
CVSS
8.1 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/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
7Source 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
8.1CVSS 3.1HighCVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H1.46Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.1High
CVSS 3.1 vector shape for CVE-2020-10061Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/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
zephyrproject-rtoszephyr2.2.0, 1.14.0Listed
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.