Mycar Controls
Approved changes feed: RSS · Atom
cpe:2.3:a:mycarcontrols:mycar_controls:*:*:*:*:*:android:*:*part: a version: * update: *
| Vendor | Mycarcontrols (4b210238-b2be-5421-9372-67619f52cfae) |
|---|---|
| Product | Mycar Controls (1a09cbf8-2d3f-5530-ba70-f047f484f2c4) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | android |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2019-9493 |
vulnerable | 2026-06-08 05:14:25.353374 |
MyCar Controls uses hard-coded credentials
MEDIUM (6.5)
The MyCar Controls of AutoMobility Distribution Inc., mobile application contains hard-coded admin credentials. A remote unauthenticated attacker may be able to send commands to and retrieve data from a target MyCar unit. This may allow the attacker to learn the location of a target, or gain unauthorized physical access to a vehicle. This issue affects AutoMobility MyCar versions prior to 3.4.24 on iOS and versions prior to 4.1.2 on Android. This issue has additionally been fixed in Carlink, Link, Visions MyCar, and MyCar Kia.
Published: 2020-01-15T17:05:27.083Z
Updated: 2024-09-17T03:27:50.908Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.