VulnerabilityPublished 6 Aug 2025

CVE-2025-8650: Kenwood DMX958XR · OS Command Injection

Affects Kenwood DMX958XRSource CVE Database V5

Not known to be exploited · CVSS 6.8 Medium.

Data as of 26 Oct 2026, 09:16 UTC

CVSS 3.0 base score

6.8Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.6% chance of exploitation in 30 days – higher than 51% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Physical
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Physical: The attack requires the attacker to physically touch or manipulate the vulnerable component. Physical interaction may be brief or persistent.
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 6 Aug 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Kenwood DMX958XR	Affected =1.0.0509.3100	Fixed in–

AI-suggested

1. Physical Security: Strengthen physical security controls around vehicles and devices to prevent unauthorized access. This includes secure parking, surveillance, and restricted access to service areas. 2. Firmware Updates: Monitor Kenwood’s official channels for firmware updates addressing this vulnerability and apply patches promptly once available. 3. Device Inventory and Segmentation: Identify all Kenwood DMX958XR devices in use and segment their network access to limit potential lateral movement if compromised. 4. Access Controls: Implement strict access policies for personnel who handle or maintain these devices, including logging and auditing physical interactions. 5. Monitoring and Detection: Deploy anomaly detection on network traffic associated with these devices to identify unusual command execution or data flows. 6. Vendor Engagement: Engage with Kenwood or authorized resellers to confirm timelines for patches and request mitigation guidance. 7. Incident Response Planning: Prepare response plans for potential device compromise scenarios, including isolating affected vehicles and forensic analysis. These steps go beyond generic advice by focusing on the physical access vector, device-specific controls, and integration with organizational security practices.

Description

Kenwood DMX958XR libSystemLib Command Injection Remote Code Execution Vulnerability. This vulnerability allows physically present attackers to execute arbitrary code on affected installations of Kenwood DMX958XR devices. Authentication is not required to exploit this vulnerability. The specific flaw exists within the firmware update process. The issue results from the lack of proper validation of a user-supplied string before using it to execute a system call. An attacker can leverage this vulnerability to execute code in the context of root. Was ZDI-CAN-26306.

Impact

For European organizations, the impact of this vulnerability depends largely on the deployment of Kenwood DMX958XR devices within their infrastructure. These devices are typically automotive multimedia receivers, so the primary risk is to organizations involved in automotive fleets, transportation services, or companies using these devices in connected vehicles or specialized equipment. An attacker with physical access could gain root-level control over the device, potentially allowing them to manipulate device functionality, intercept or alter data streams, or pivot to other connected systems if network interfaces are exposed. This could lead to operational disruptions, data breaches, or safety risks in transportation contexts. Given the physical access requirement, the threat is more acute in environments where devices are accessible to unauthorized personnel, such as fleet vehicles parked in unsecured locations or service centers. The lack of authentication for exploitation increases risk in such scenarios. While the vulnerability does not directly affect enterprise IT systems, the growing integration of automotive devices into broader IoT and enterprise networks means that compromise could serve as a foothold for lateral movement or espionage. The medium CVSS score reflects these nuanced risks.

CWE-78Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #9OWASP Top 10 A05:2025: Injection (opens in a new tab)
The product constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command when it is sent to a downstream component.
Architecture and Design
If at all possible, use library calls rather than external processes to recreate the desired functionality.
Architecture and Design · Operation · Sandbox or Jail
Run the code in a "jail" or similar sandbox environment that enforces strict boundaries between the process and the operating system. This may effectively restrict which files can be accessed in a particular directory or which commands can be executed by the software.
Architecture and Design · Attack Surface Reduction
For any data that will be used to generate a command to be executed, keep as much of that data out of external control as possible. For example, in web applications, this may require storing the data locally in the session's state instead of sending it out to the client in a hidden form field.
OWASP Cheat Sheets
Injection Prevention (opens in a new tab)
Injection Prevention in Java (opens in a new tab)
OS Command Injection Defense (opens in a new tab)
Abuse Case (opens in a new tab)
Deserialization (opens in a new tab)
OWASP ASVS 4.0.3
V12.3.5 (opens in a new tab)
V5.3.8 (opens in a new tab)
V1.5.1 (opens in a new tab)
Attack patterns
Command Line Execution through SQL Injection (opens in a new tab)
Command Delimiters (opens in a new tab)
Exploiting Multiple Input Interpretation Layers (opens in a new tab)
Argument Injection (opens in a new tab)
OS Command Injection (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

zerodayinitiative.com/advisories/ZDI-25-798/ (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 6 Aug 2025, 02:20 UTC

WeaknessesCWE-78

Technical details

References

Community reviews

Related threats