dbcve.org
InfotainmentApplication · Visteon

CVE-2024-8358

MEDIUM · 6.8 CVSS v3.1 Published 2024-11-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
73/100
Remediation priority · Elevated
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
Visteon Infotainment UPDATES_ExtractFile Command Injection Remote Code Execution Vulnerability. This vulnerability allows physically present attackers to execute arbitrary code on affected installations of Visteon Infotainment systems. Authentication is not required to exploit this vulnerability. The specific flaw exists within the UPDATES_ExtractFile function. A crafted software update file can trigger execution of a system call composed from a user-supplied string. An attacker can leverage this vulnerability to execute code in the context of the device. Was ZDI-CAN-23422.

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

A command injection vulnerability exists in the UPDATES_ExtractFile function of Visteon Infotainment systems. Attackers can craft a malicious software update file containing system commands embedded in user-supplied strings, which get executed when the system processes the update. This allows arbitrary code execution in the device context without authentication, though physical access to the system is required.

MitigationObtain and apply the vendor-supplied firmware/security patch from Visteon to remediate the command injection in UPDATES_ExtractFile. Until the patch is available, restrict physical access to infotainment systems and verify the integrity of any software updates using vendor-provided cryptographic signatures.

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
InfotainmentApplication
Affected:= cmu150_na_74.00.324a

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
Physical
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:P/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. Identify the infotainment system model
    Locate the system information or firmware version on the Visteon infotainment unit, typically accessible through the system settings menu, diagnostic port, or by examining the boot logs.
    Affected if The system is a Visteon Infotainment unit, but the exact model/version cannot be determined or does not match the affected version.
  2. Check the installed firmware version
    Compare the installed firmware version against the affected version cmu150_na_74.00.324a. This may be visible in system settings under 'About' or 'Software Information', or obtainable via diagnostic tools connected to the infotainment system.
    Affected if The installed firmware version is exactly cmu150_na_74.00.324a, indicating the system is running the affected version.
  3. Verify software update feature status
    Determine whether the software update functionality is enabled or accessible on the infotainment system. This may involve checking system configuration menus, looking for update-related services, or examining which update mechanisms are available.
    Affected if Software update features are enabled and the system accepts update files, making the UPDATES_ExtractFile function accessible for processing incoming update packages.
  4. Inspect for unknown or suspicious update files
    Examine any software update files present on the system or stored externally that may have been used for updates. Look for update packages that were not obtained directly from the vendor or that contain unexpected content.
    Affected if A software update file exists on the system that was not sourced from official Visteon channels or contains unexpected command strings within update metadata.

The system is affected if it is a Visteon Infotainment unit running firmware version cmu150_na_74.00.324a with software update functionality enabled, allowing the UPDATES_ExtractFile function to process malicious update files.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Obtain and apply the vendor-supplied firmware/security patch from Visteon to remediate the command injection in UPDATES_ExtractFile. Until the patch is available, restrict physical access to infotainment systems and verify the integrity of any software updates using vendor-provided cryptographic signatures.

Fix this in Infotainment Scoped from the published advisory
  • Consultation8.0 h
  • Implementation4.0 h
  • Testing12.0 h
  • Review / QA6.0 h
30.0 hours of engineering $5,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-8358 — 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-2024-8358 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