Mobile Devices has a narrow vulnerability footprint centered on automotive diagnostic firmware, specifically OBD-II dongle implementations that interface with vehicle systems. The recurring signal involves data-authenticity and validation concerns in firmware-level components; current severity, exploitation, and exposure counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Mobile Devices over time
Signals from CVEs in this vendor scope (3 CVEs).
3 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2015-2907HIGH Mobile Devices (aka MDI) C4 OBD-II dongles with firmware 2.x and 3.4.x, as used in Metromile Pulse and other products, have hardcoded SSH credentials, which makes it easier for rem | Aug 23, 2015 | 9.0 | 23 | NO | NO |
CVE-2015-2906HIGH 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 cus | Aug 23, 2015 | 9.0 | 23 | NO | NO |
CVE-2015-2908HIGH 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 attacke | Aug 23, 2015 | 9.0 | 22 | NO | NO |
Signals from CVEs in this vendor scope (3 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Mobile Devices.
Media articles that mention a CVE ID that affects a product developed by Mobile Devices — matched by CVE ID, not by vendor name.