C4B OBD-II Dongle 2.x/3.4.x SSH Key improper authentication ⚔ [Disputed]
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in C4B OBD-II Dongle 2.x/3.4.x and classified as critical. The impacted element is an unknown function of the component SSH Key. The manipulation leads to improper authentication. This vulnerability is documented as CVE-2015-2906. There is not any exploit available. The presence of this vulnerability remains uncertain at this time. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Details
A vulnerability was found in C4B OBD-II Dongle 2.x/3.4.x. It has been rated as critical. This issue affects an unknown part of the component SSH Key. The manipulation with an unknown input leads to a improper authentication vulnerability. Using CWE to declare the problem leads to CWE-287. When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. Impacted is 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, store SSH private keys that are the same across different customers' installations, which makes it easier for remote attackers to obtain access by leveraging knowledge of a private key from another installation. NOTE: the vendor states "This was a flaw for the developer/debugging devices (again not possible in production versions)."
The weakness was released 08/23/2015 (Website). The advisory is shared at kb.cert.org. The identification of this vulnerability is CVE-2015-2906 since 04/03/2015. The attack may be initiated remotely. A simple authentication is necessary for exploitation. Neither technical details nor an exploit are 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.
Entries connected to this vulnerability are available at VDB-77382 and VDB-77383. 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: 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: Improper authenticationCWE: CWE-287
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-2906 (🔍)
GCVE (CVE): GCVE-0-2015-2906
GCVE (VulDB): GCVE-100-77381
CERT: 🔍
See also: 🔍
Entry
Created: 08/24/2015 10:15 AMUpdated: 11/07/2024 02:15 PM
Changes: 08/24/2015 10:15 AM (42), 10/27/2017 08:06 PM (8), 11/07/2024 02:15 PM (17)
Complete: 🔍
Cache ID: 244:E60:40
No comments yet. Languages: en.
Please log in to comment.