C4B OBD-II Dongle 2.x/3.4.x Firmware Update data authenticity ⚔ [Disputed]
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in C4B OBD-II Dongle 2.x/3.4.x. It has been classified as critical. This impacts an unknown function of the component Firmware Update Handler. This manipulation causes data authenticity. This vulnerability appears as CVE-2015-2908. There is no available exploit. There is ongoing doubt regarding the real existence of this vulnerability.
Details
A vulnerability classified as critical was found in C4B OBD-II Dongle 2.x/3.4.x. Affected by this vulnerability is an unknown code block of the component Firmware Update Handler. The manipulation with an unknown input leads to a data authenticity vulnerability. The CWE definition for the vulnerability is CWE-345. The product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
** DISPUTED ** Mobile Devices (aka MDI) C4 OBD-II dongles with firmware 2.x and 3.4.x, as used in Metromile Pulse and other products, do not validate firmware updates, which allows remote attackers to execute arbitrary code by specifying an update server. NOTE: the vendor states "This was a flaw for the developer/debugging devices, and was fixed in production version about 3 years ago."
The weakness was presented 08/23/2015 (Website). It is possible to read the advisory at kb.cert.org. This vulnerability is known as CVE-2015-2908 since 04/03/2015. The attack can be launched remotely. The requirement for exploitation is a single authentication. The technical details are unknown and an exploit is not publicly available.
The real existence of this vulnerability is still doubted at the moment.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
See VDB-77381 and VDB-77382 for similar entries. Be aware that VulDB is the high quality source for vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 6.3
VulDB Base Score: 6.3
VulDB Temp Score: 6.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
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: 🔍
NVD Base Score: 🔍
Exploiting
Class: Data authenticityCWE: CWE-345
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
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
04/03/2015 🔍08/23/2015 🔍
08/23/2015 🔍
08/24/2015 🔍
11/07/2024 🔍
Sources
Advisory: kb.cert.orgStatus: Not defined
Confirmation: 🔍
Disputed: 🔍
CVE: CVE-2015-2908 (🔍)
GCVE (CVE): GCVE-0-2015-2908
GCVE (VulDB): GCVE-100-77383
CERT: 🔍
See also: 🔍
Entry
Created: 08/24/2015 10:15Updated: 11/07/2024 17:58
Changes: 08/24/2015 10:15 (47), 10/28/2017 10:07 (2), 11/07/2024 17:58 (17)
Complete: 🔍
Cache ID: 216::103
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.