dbcve.org
Mycar ControlsApplication · Mycarcontrols

CVE-2019-9493

CRITICAL · 9.8 CVSS v3.1 Published 2020-01-15
Fix available
A fix is available. Upgrade to 3.4.24 / 4.1.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The MyCar Controls mobile application contains hard-coded admin credentials embedded in the application code. A remote unauthenticated attacker can exploit these credentials to authenticate to the MyCar backend API, sending arbitrary commands to connected vehicle units and retrieving sensitive data including real-time location information. This allows potential unauthorized physical access to vehicles.

MitigationUpdate MyCar Controls to version 3.4.24 or later (iOS) and 4.1.2 or later (Android). Apply updates to affected related applications (Carlink, Link, Visions MyCar, MyCar Kia). Investigate potential credential exposure and rotate credentials if compromise is suspected.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Mycar ControlsApplication
Affected:< 3.4.24< 4.1.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check MyCar Controls iOS version
    On the iOS device, go to Settings > MyCar Controls > Version, or view the app version listed in the iOS App Store or iTunes. Record the version number.
    Affected if Version is lower than 3.4.24
  2. Check MyCar Controls Android version
    On the Android device, go to Settings > Apps > MyCar Controls > Version info, or view the app version in the Google Play Store. Record the version number.
    Affected if Version is lower than 4.1.2
  3. Check related applications for exposure
    Identify and check installed versions of related apps: Carlink, Link, Visions MyCar, and MyCar Kia. Check each app's version through Settings or the respective app store.
    Affected if Any related application is present and has an exposed version from the same vulnerable code base
  4. Compare against affected ranges
    Take the recorded version numbers and compare them to the affected ranges: iOS versions below 3.4.24 and Android versions below 4.1.2 are in the vulnerable range.
    Affected if Any installed version falls below the corresponding threshold for its platform

If MyCar Controls or its related applications are installed at versions below 3.4.24 on iOS or below 4.1.2 on Android, the hard-coded credentials are present and the environment is affected.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 3.4.24 / 4.1.2 or later
Fixed in 3.4.244.1.2
Interim mitigation

Update MyCar Controls to version 3.4.24 or later (iOS) and 4.1.2 or later (Android). Apply updates to affected related applications (Carlink, Link, Visions MyCar, MyCar Kia). Investigate potential credential exposure and rotate credentials if compromise is suspected.

Recommended fix High confidence

MyCar Controls 3.4.24 (iOS) / 4.1.2 (Android) or later

  1. Update MyCar Controls mobile application from the iOS App Store to version 3.4.24 or later
  2. Update MyCar Controls mobile application from the Google Play Store to version 4.1.2 or later
  3. If using Carlink, Link, Visions MyCar, or MyCar Kia variants, ensure they are updated to their latest versions

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Mycar Controls Scoped from the published advisory
  • Consultation6.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,184.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-9493 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-9493 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data