dbcve.org
InfotainmentApplication · Visteon

CVE-2024-8360

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 REFLASH_DDU_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 REFLASH_DDU_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-23421.

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

Visteon Infotainment systems contain a command injection vulnerability in the REFLASH_DDU_ExtractFile function. A physically present attacker can craft a malicious software update file containing a user-supplied string that gets incorporated into a system call, allowing arbitrary code execution in the device context. No authentication is required.

MitigationApply vendor-supplied firmware patches when available. As a compensating control, restrict physical access to the infotainment system and validate software update files through cryptographic signatures before processing.

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 brand and model
    Inspect the head unit physically or check vehicle documentation for the infotainment system manufacturer and model number. Visteon systems typically display the vendor in system information or settings.
    Affected if The system is not a Visteon Infotainment unit
  2. Retrieve the installed firmware version
    Access the infotainment system settings menu, typically under Settings > System > About or similar. Alternatively, use the vehicle diagnostic port with appropriate tooling to query the infotainment module for its software version string.
    Affected if Unable to retrieve a version string from the system
  3. Compare installed version against the affected version
    Match the retrieved firmware version string exactly against 'cmu150_na_74.00.324a'. Note that this vulnerability affects only this specific version.
    Affected if The installed version is exactly cmu150_na_74.00.324a
  4. Check if software update functionality is present
    Look for REFLASH, Software Update, or DDU Update options in the infotainment system menu. This feature is typically found under Settings > Software Update or Settings > System Maintenance.
    Affected if The software update/REFLASH feature exists on the system and accepts external files

You are affected if your Visteon Infotainment system runs exactly version cmu150_na_74.00.324a and the software update/REFLASH functionality is accessible to a physically present attacker.

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

Apply vendor-supplied firmware patches when available. As a compensating control, restrict physical access to the infotainment system and validate software update files through cryptographic signatures before processing.

Fix this in Infotainment Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,360
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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