External risk intelligence

OS Command Injection in Network-Connected Devices Allows Full System Compromise

CVE advisorySeverity: CRITICAL (CVSS 10.0)

CVE-2025-64128

The vulnerability affects Zenitel IP intercom and public address devices, which are designed to be network-connected and are frequently deployed as internet-facing or edge-connected infrastructure. Because these devices are intended for external communication and often feature unauthenticated or pre-auth web management interfaces, the attack surface is public-facing by design.

OS Command Injection

Halo Surface Signal: 5 out of 5 — more likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

An OS command injection vulnerability exists due to incomplete validation of user-supplied input, potentially allowing unauthenticated attackers to execute arbitrary commands on affected systems. The main concern is confirming relevance and exposure.

  • Attackers can inject commands into systems.
  • Critical systems could be remotely controlled.
  • Verify if these specific devices are in use.

Attack Path

How an attacker could exploit the issue

An attacker can exploit this vulnerability by sending specially crafted input to a vulnerable system over the network. Because the system does not properly validate user input, the attacker can inject arbitrary commands, potentially leading to a complete compromise of the device.

  • Network access is required.
  • Input validation flaws are triggered.
  • Unauthenticated command execution occurs.

Live Threat

Current exploitation, exposure, and threat context

An OS command injection vulnerability exists when user input is not properly validated, potentially allowing attackers to append arbitrary data and execute commands. This could affect system data and service behavior under specific conditions, allowing unauthenticated attackers to inject commands.

  • System commands and data.
  • Unauthenticated network access.
  • Arbitrary command execution.

Operational Fix

Recommended remediation, mitigation, and detection steps

This OS command injection vulnerability, likely affecting network-connected communication devices, requires immediate attention from teams responsible for their management and security. The first practical step is to inventory all instances of the affected technology, determine their network exposure and business criticality, identify the accountable owner for each instance, and then prioritize remediation efforts based on risk.

  • Identify and confirm accountable owners.
  • Verify network exposure and criticality.
  • Plan remediation based on risk.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is the software affected by CVE-2025-64128?

This vulnerability affects Zenitel IP intercom and public address systems. These devices are used for critical communication and public address functions in various environments, serving as network-connected infrastructure that facilitates both voice communication and institutional messaging.

How does this OS command injection work?

The software fails to properly check user-supplied input, a weakness classified as CWE-78 (OS Command Injection). Because the input validation is incomplete, an attacker can append malicious data to legitimate requests. This tricks the underlying operating system into executing unauthorized commands with the privileges of the application.

Do I need to be authenticated to trigger this flaw?

No, authentication is not required to trigger this vulnerability. The flaw exists because the system processes unsanitized input from the network. It is not triggered by administrative actions or authorized configuration changes, but rather by sending specially crafted input designed to bypass input filters.

How do I know if my devices are relevant?

According to Halo Surface Signal, these devices are designed for network connectivity and are frequently deployed as internet-facing or edge-connected infrastructure. You should consider any instance of this hardware that is reachable over your network, particularly those with interfaces exposed to the public internet, to be at risk.

What is the recommended first step for owners?

Begin by building an inventory of all Zenitel devices within your environment. Once identified, assess the network placement of each unit to determine if they are exposed to the internet or reachable from untrusted network segments. Establish who owns each device to coordinate patching or access restriction plans.

References