Preh Car Connect Volkswagen MIB3 Infotainment System MIB3 OI MQB up to 0304 Bluetooth Stack integer overflow
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.4 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Preh Car Connect Volkswagen MIB3 Infotainment System MIB3 OI MQB up to 0304. It has been rated as problematic. This affects an unknown function of the component Bluetooth Stack. This manipulation causes integer overflow. This vulnerability is tracked as CVE-2023-28908. The attack is only possible within the local network. No exploit exists.
Details
A vulnerability was found in Preh Car Connect Volkswagen MIB3 Infotainment System MIB3 OI MQB up to 0304. It has been declared as problematic. Affected by this vulnerability is an unknown function of the component Bluetooth Stack. The manipulation with an unknown input leads to a integer overflow vulnerability. The CWE definition for the vulnerability is CWE-190. The product performs a calculation that can produce an integer overflow or wraparound, when the logic assumes that the resulting value will always be larger than the original value. This can introduce other weaknesses when the calculation is used for resource management or execution control. As an impact it is known to affect integrity, and availability. The summary by CVE is:
A specific flaw exists within the Bluetooth stack of the MIB3 infotainment. The issue results from the lack of proper validation of user-supplied data, which can result in an integer overflow when receiving non-fragmented HCI packets on a channel. 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.
The weakness was disclosed by Mikhail Evdokimov. The advisory is shared at i.blackhat.com. This vulnerability is known as CVE-2023-28908 since 03/27/2023. The exploitation appears to be easy. The attack needs to approached within the local network. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 07/01/2025).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2023-32528). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.4VulDB Meta Temp Score: 5.4
VulDB Base Score: 5.4
VulDB Temp Score: 5.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 5.4
CNA Vector (ASRG): 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Integer overflowCWE: CWE-190 / CWE-189
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Partially
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
03/27/2023 🔍06/28/2025 🔍
06/28/2025 🔍
07/01/2025 🔍
Sources
Advisory: i.blackhat.comResearcher: Mikhail Evdokimov
Status: Not defined
CVE: CVE-2023-28908 (🔍)
GCVE (CVE): GCVE-0-2023-28908
GCVE (VulDB): GCVE-100-314377
EUVD: 🔍
Entry
Created: 06/28/2025 18:05Updated: 07/01/2025 10:19
Changes: 06/28/2025 18:05 (62), 06/28/2025 19:41 (1), 07/01/2025 10:19 (1)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.