OS command injection in FFRI Security, Inc. FFRI AMC enables remote command execution

Note: This data is for reference and cybersecurity research purposes only.CyStack advises users not to use this information for unlawful purposes.

Overview

Original source data

FFRI AMC versions 3.4.0 to 3.5.3 and some OEM products that implement/bundle FFRI AMC versions 3.4.0 to 3.5.3 allow a remote unauthenticated attacker to execute arbitrary OS commands when certain conditions are met in an environment where the notification program setting is enabled and the executable file path is set to a batch file (.bat) or command file (.cmd) extension.

Affected products and scope

  • FFRI Security, Inc. FFRI AMC: affected in the 3.4.0 through 3.4.6 and 3.5.0 through 3.5.3 branches. The published fix is 3.6.1.
  • NEC Corporation FFRI AMC for ActSecure χ: affected in the 3.4.0 through 3.4.6 and 3.5.0 through 3.5.3 branches. The published fix is 3.6.1.
  • Sky Co., Ltd. EDR Plus Pack: affected when the package bundles FFRI AMC from the branches listed above. The published fix is the package containing FFRI AMC 3.6.1.
  • JVN states that FFRI yarai Cloud, FFRI yarai, FFRI yarai Home and Business Edition, and other FFRI yarai OEM products outside the listed products are not affected. Sky Co., Ltd. also states that EDR Plus Pack Cloud is not affected.

Technical details

FFRI Security, Inc. FFRI AMC is a management console for the FFRI yarai and ActSecure χ endpoint security products. The confirmed weakness is OS command injection, classified as CWE-78, in notification program processing when that setting is enabled and the executable path points to a .bat or .cmd file. JVN states that an attacker can impersonate a yarai client and send a crafted request to FFRI AMC, causing an arbitrary OS command to execute on the affected server. The exact condition involving how the file must be written or formatted is not described in detail in the public sources reviewed. The command runs with the privilege of the FFRI AMC process; JVN states that the initial configuration uses the LocalSystem account.

Exploitability

The vulnerability is reachable over the network by an unauthenticated attacker when the notification program is enabled and the executable path is configured for a .bat or .cmd extension. The described attack flow is for the attacker to impersonate a yarai client and send a crafted request to FFRI AMC. The normalized record marks user interaction as required, while the published JVN analysis marks user interaction as not required; the reviewed advisories do not explain this discrepancy. The supplied record does not identify a public exploit, and FFRI stated that, at the time of its advisory, it had received no related reports or inquiries and had not recognized an actual attack. That statement does not establish that exploitation is absent now.

Technical impact

FFRI AMC can execute arbitrary OS commands on the server when a crafted request is processed under the vulnerable configuration. JVN states that the command runs with the same privilege as the FFRI AMC process and that the initial configuration uses LocalSystem, so possible consequences include unauthorized server changes, access to resources available to the service account, and service disruption. The scope is described as unchanged because execution occurs within the privilege context of the affected product. The public sources do not confirm a specific data theft event, breach, or compromise of managed endpoints.

Business impact

  • The FFRI AMC server may execute commands with the product process privilege; JVN describes the initial configuration as using LocalSystem, so the potential effect on server integrity can be substantial.
  • An attacker may be able to alter local data or configuration, access resources available to the service account, or disrupt security administration. These are possible consequences of arbitrary command execution, not a confirmed breach scenario.
  • Compromise of the management server could undermine administration of FFRI yarai or ActSecure χ, but the reviewed sources do not confirm compromise of managed endpoints.
  • Organizations should prioritize identifying systems with the vulnerable configuration, applying the fix, and using the documented workaround if immediate updating is not possible.

Remediation

  1. Update: upgrade FFRI AMC to 3.6.1. For FFRI AMC for ActSecure χ, use version 3.6.1 supplied by NEC Corporation. For EDR Plus Pack, update to the package containing FFRI AMC 3.6.1 according to Sky Co., Ltd.'s guidance.
  2. Workaround if updating is not immediately possible: disable the notification program setting. This removes the documented exposure condition but also disables the notification functionality provided by that setting.
  3. Alternative workaround: if the notification program must remain enabled, configure the executable name or executable path to a program that does not use the .bat or .cmd extension.
  4. Reduce exposure: restrict which endpoints can access FFRI AMC and limit access from untrusted networks. These measures reduce exploitation opportunity but do not replace the update.
  5. After remediation, recheck the notification program configuration and the actual FFRI AMC version, including the version bundled by any OEM product.

Detection

  1. Inventory standalone FFRI AMC deployments and OEM products that implement or bundle FFRI AMC, then compare each installed branch with the affected and fixed boundaries in affected_summary.
  2. Inspect the notification program configuration on each server. Flag systems where the setting is enabled and the executable path points to a .bat or .cmd file.
  3. Review network telemetry and application logs for unusual requests claiming to originate from yarai clients, together with command execution activity created by the FFRI AMC process.
  4. Confirm the actual FFRI AMC version or the bundled FFRI AMC version after remediation.
  5. The public advisories do not provide specific IOCs, event IDs, or log signatures. Absence of those signs does not prove that a system is safe; the request and command-execution checks above are precautionary monitoring.
Sources (18)
Learn more

Run an in-depth assessment with complete web risk management

CyStack VulnScan continuously discovers assets, validates vulnerabilities, and helps security teams prioritize remediation across the organization.