dbcve.org
Integer OverflowWeakness · CWE-190

CVE-2023-28909

HIGH · 8.0 CVSS v3.1 Published 2025-06-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
83/100
Remediation priority · High
No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A specific flaw exists within the Bluetooth stack of the MIB3 unit. The issue results from the lack of proper validation of user-supplied data, which can result in an integer overflow when receiving fragmented HCI packets on a channel. An attacker can leverage this vulnerability to bypass the MTU check on a channel with enabled fragmentation. Consequently, this can lead to a buffer overflow in upper layer profiles, which can be used to obtain remote code execution. The vulnerability was originally discovered in Skoda Superb III car with MIB3 infotainment unit OEM part number 3V0035820. The list of affected MIB3 OEM part numbers is provided in the referenced resources.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A vulnerability exists in the Bluetooth stack of the MIB3 infotainment unit where improper validation of user-supplied data during fragmented HCI packet reception leads to an integer overflow. This allows bypassing MTU checks on channels with enabled fragmentation, resulting in a buffer overflow in upper layer profiles that can be exploited for remote code execution.

MitigationThe vendor must issue a firmware update for affected MIB3 units that adds proper validation of user-supplied data to prevent integer overflow in the Bluetooth stack's HCI packet handling. Users should apply the update through authorized dealership service channels.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Adjacent
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm MIB3 infotainment unit in use
    Check vehicle infotainment system model through system settings or vehicle documentation. MIB3 units are found in Volkswagen Group vehicles (VW, Audi, Skoda, Seat).
    Affected if System is not a MIB3 unit - different infotainment platforms are not affected by this specific vulnerability
  2. Verify Bluetooth is enabled
    Access infotainment Bluetooth settings and confirm Bluetooth functionality is turned on. The vulnerability occurs during HCI (Host Controller Interface) packet reception.
    Affected if Bluetooth is disabled - the vulnerability requires active Bluetooth stack operation to be exploitable
  3. Check Bluetooth fragmentation configuration
    Inspect Bluetooth settings for channel fragmentation options. This varies by infotainment interface - look for settings related to Bluetooth channel configuration, fragmentation, or advanced Bluetooth protocols.
    Affected if Fragmentation is disabled on all Bluetooth channels - the flaw specifically bypasses MTU checks on channels with enabled fragmentation
  4. Determine firmware version
    Access infotainment system info or diagnostics menu to retrieve the firmware version. Compare against vendor-released patch version numbers for CVE-2023-28909 when available through official channels.
    Affected if Installed firmware version matches the vulnerable version range published by the vehicle manufacturer

A user is affected if they have a MIB3 infotainment unit with Bluetooth enabled and fragmentation configured on Bluetooth channels, running a firmware version within the vulnerable range published by the vehicle manufacturer.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

The vendor must issue a firmware update for affected MIB3 units that adds proper validation of user-supplied data to prevent integer overflow in the Bluetooth stack's HCI packet handling. Users should apply the update through authorized dealership service channels.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA6.0 h
34.0 hours of engineering $5,940
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,504.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-28909 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-28909 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data