CVE-2023-28910

Bluetooth assertion bypass via cleared abortion flag

Published Jun 28, 2025 · Updated Jun 30, 2025

Improper exceptional-condition handling in JOYNEXT MIB3 OI MQB firmware through 0304 allows attackers to bypass Bluetooth stack assertions. The Initializer::requestInitLocalDevice callback clears the global bAbortion flag, so BGLOG_Assert logs invalid states without terminating the phone-service process. Bluetooth pairing and a separate L2CAP integer-overflow flaw are required to turn the bypass into code execution with an IVI system shell.

CVSS severity8.0
High
EPSS probability0.35%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Improper exceptional-condition handling in JOYNEXT MIB3 OI MQB firmware through 0304 allows attackers to bypass Bluetooth stack assertions. The Initializer::requestInitLocalDevice callback clears the global bAbortion flag, so BGLOG_Assert logs invalid states without terminating the phone-service process. Bluetooth pairing and a separate L2CAP integer-overflow flaw are required to turn the bypass into code execution with an IVI system shell.

The record

CVE
CVE-2023-28910
Published
Jun 28, 2025
Updated
Jun 30, 2025
Vendor
JOYNEXT GmbH
Product
JOYNEXT MIB3 OI MQB
Classifications
CWE-754, CAPEC-554, T1203
Attack vector
adjacent
Privileges
unauthenticated

Timeline

How it unfolded

  1. Jun 28, 2025CVE publishedPublication date reported by the CVE source.
  2. Jun 30, 2025Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=0 <=0304

What conditions does exploitation require?

Attack vectoradjacent
Required privilegesunauthenticated

What is affected?

JOYNEXT GmbH · JOYNEXT MIB3 OI MQBversion=0 <=0304

Published CVSS scores

8.0Automotive Security Research GroupCVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectoradjacent
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-754Improper Check for Unusual or Exceptional Conditions
CAPEC-554Functionality Bypass
T1203Exploitation for Client Execution

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo