PREH MIB3 Infotainment Unit up to 0304 Real-Time Streaming Protocol /logs ID parameters
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in PREH MIB3 Infotainment Unit up to 0304. Impacted is an unknown function of the file /logs of the component Real-Time Streaming Protocol Handler. Performing a manipulation of the argument ID with the input 0 results in improper handling of parameters.
This vulnerability is cataloged as CVE-2023-28898. The attack must originate from the local network. There is no exploit available.
Details
A vulnerability was found in PREH MIB3 Infotainment Unit up to 0304. It has been classified as problematic. This affects an unknown functionality of the file /logs of the component Real-Time Streaming Protocol Handler. The manipulation of the argument id with the input value 0 leads to a improper handling of parameters vulnerability. CWE is classifying the issue as CWE-233. The product does not properly handle when the expected number of parameters, fields, or arguments is not provided in input, or if those parameters are undefined. This is going to have an impact on availability. The summary by CVE is:
The Real-Time Streaming Protocol implementation in the MIB3 infotainment incorrectly handles requests to /logs URI, when the id parameter equals to zero. This issue allows an attacker connected to the in-vehicle Wi-Fi network to cause denial-of-service of the infotainment system, when the certain preconditions are met. Vulnerability discovered on Škoda Superb III (3V3) - 2.0 TDI manufactured in 2022.
The weakness was shared 01/12/2024 by Aleksei Stennikov. This vulnerability is uniquely identified as CVE-2023-28898 since 03/27/2023. Technical details are known, but no exploit is available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.3
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 5.3
CNA Vector (Automotive Security Research Group (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: Improper handling of parametersCWE: CWE-233 / CWE-229 / CWE-20
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 🔍01/12/2024 🔍
01/12/2024 🔍
01/12/2024 🔍
Sources
Researcher: Aleksei StennikovStatus: Not defined
CVE: CVE-2023-28898 (🔍)
GCVE (CVE): GCVE-0-2023-28898
GCVE (VulDB): GCVE-100-250629
Entry
Created: 01/12/2024 17:34Changes: 01/12/2024 17:34 (50)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.