LiveActive security incident?Get immediate response
CVE Record

CVE-2023-2234: BT HCI host union variant confusion

Union variant confusion allows any malicious BT controller to execute arbitrary code on the Zephyr host.

MediumCVSS 6.8Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-2234 is a Zephyr Bluetooth host flaw where a malicious Bluetooth controller could cause code execution on the Zephyr host. The business risk is concentrated in embedded products that pair Zephyr with Bluetooth controller hardware, especially where that controller can be replaced, compromised, or sourced from an untrusted supply chain.

Executive priority

Prioritize products where attackers, technicians, or supply-chain actors could influence Bluetooth controller hardware or firmware. This is not evidenced as actively exploited, but arbitrary code execution on embedded hosts can create serious product integrity and safety concerns.

Technical view

The issue is CWE-843 union variant confusion in Zephyr's BT HCI host handling. The CVSS vector is AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, meaning physical access is required but no privileges or user interaction are needed, and successful exploitation can fully compromise confidentiality, integrity, and availability.

Likely exposure

Exposure is likely limited to Zephyr-based devices using Bluetooth HCI host functionality with a controller that could be malicious or physically introduced. The provided data lists Zephyr as affected but does not identify specific releases, downstream products, or fixed versions.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. The described attacker is a malicious Bluetooth controller, and the CVSS vector requires physical access. Treat internet-scale remote exploitation as unsupported by the supplied evidence.

Researcher notes

Key unknowns are the exact affected Zephyr versions, patch commits, and downstream vendor exposure. The CVE data supports the impact and attack preconditions but does not provide enough detail to name a fix or confirm exploit availability.

Mitigation direction

  • Review the Zephyr security advisory for affected releases and fixed versions.
  • Apply vendor or Zephyr-maintained updates when a fixed release is identified.
  • Restrict devices to trusted Bluetooth controller hardware and approved firmware.
  • Disable Bluetooth functionality where it is not operationally required.
  • Assess supply-chain controls for Bluetooth modules in affected products.

Validation and detection

  • Inventory products and firmware builds that include Zephyr Bluetooth support.
  • Confirm whether each design uses a separate or replaceable Bluetooth controller.
  • Map deployed firmware to Zephyr versions and vendor backports.
  • Review the Zephyr advisory and product vendor notices for fix status.
  • Verify updated builds through normal regression and Bluetooth compatibility testing.
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-843: 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
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-2234 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
Medium
CVSS
6.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:P/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
6.8CVSS 3.1MediumCVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H0.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.8Medium
CVSS 3.1 vector shape for CVE-2023-2234Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:P/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
zephyrproject-rtosZephyrZephyr, *unaffected
Weakness

CWE details

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

CWE-843 · source CWE mapping

Access of Resource Using Incompatible Type ('Type Confusion')

Access of Resource Using Incompatible Type ('Type Confusion') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.