CVE-2024-0400: Hitachi Energy MACH SCM · Code Injection
Affects Hitachi Energy MACH SCMSource CVE Database V5
Not known to be exploited · CVSS 7.5 High.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 49% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 27 Mar 2024
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 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Hitachi Energy MACH SCM | Affected
| Fixed in– |
AI-suggested
1. Immediately review and restrict access to the MACH SCM system, ensuring only trusted and necessary system manager clients have authenticated access. 2. Implement strict network segmentation and firewall rules to limit SCM server exposure to only authorized management networks. 3. Monitor and log LINQ query activity on the SCM server for anomalous or suspicious patterns indicative of code injection attempts. 4. Enforce strong authentication mechanisms, including multi-factor authentication (MFA), to reduce risk of credential compromise. 5. Conduct regular audits of user privileges and remove unnecessary system manager client accounts. 6. Engage with Hitachi Energy for official patches or updates addressing CVE-2024-0400 and apply them promptly once available. 7. Consider deploying application-layer intrusion detection or web application firewalls capable of detecting and blocking malicious LINQ queries. 8. Prepare incident response plans specific to SCM server compromise scenarios to enable rapid containment and recovery. 9. Educate system administrators and security teams about this vulnerability and the risks of code injection in LINQ queries. 10. If patching is delayed, consider temporary mitigations such as disabling LINQ query functionality or restricting query capabilities to safe subsets if feasible.
Description
SCM Software is a client and server application. An Authenticated System manager client can execute LINQ query in the SCM server, for customized filtering. An Authenticated malicious client can send a specially crafted code to skip the validation and execute arbitrary code (RCE) on the SCM Server remotely. Malicious clients can execute any command by using this RCE vulnerability.