Fuji Electric Monitouch V-SFT code execution flaws
Free public brief. The indicators, the detections with Splunk SPL already written (plus Elastic and KQL where they apply), and a Slack alert the next time this touches a vendor you run are in the app — free account, no card.
Three memory corruption vulnerabilities in Fuji Electric screen configuration software allow local arbitrary code execution; update to v6.2.3.0.
Fuji Electric's Monitouch V-SFT, a screen configuration application used in critical manufacturing and energy sectors worldwide, contains three critical vulnerabilities that permit arbitrary code execution. Two type confusion flaws (CVE-2024-5271, CVE-2024-5597) and one stack-based buffer overflow (CVE-2024-34171) all stem from memory handling defects. Each carries a CVSS v4.0 score of 8.5, indicating high severity with low attack complexity. All three vulnerabilities require local access and user interaction; they are not remotely exploitable. CISA confirms no public exploitation has been reported as of the advisory date.
Affected versions are all releases prior to 6.2.3.0. Fuji Electric has issued a patch; the primary mitigation is immediate update. Organizations should apply network segmentation (ICS systems isolated from business networks and internet), enforce access controls, and use VPNs for any required remote access. Given the sector criticality and the straightforward nature of the flaws, patching should be prioritized despite the absence of wild exploitation reports.
Mentioned in this report
Detection guidance
Fuji Electric V-SFT Editor Spawning Shell or Script Interpreter
V-SFT screen editor spawning a command shell, script host or LOLBin, which is consistent with code execution after a memory-corruption flaw (CVE-2024-5271, CVE-2024-5597, CVE-2024-34171) is triggered by a crafted project file. Auto-generated starting point — validate and tune in your environment before deploying. IOC matches can false-positive on shared infrastructure and decay as adversary infrastructure rotates.
title: Fuji Electric V-SFT Editor Spawning Shell or Script Interpreter
id: 53b91736-ecf0-5622-8fc0-46fb2e5ac359
status: experimental
description: Detects the Monitouch V-SFT screen editor spawning a command shell, script
host or common LOLBin. The V-SFT advisory describes type confusion and stack buffer
overflow flaws that give local code execution when a crafted file is opened. The
editor has no normal need to launch interpreters, so a child process of this kind
suggests post-exploitation. The parent image match is based on the product name
and may need tuning to the deployed executable name.
tags:
- attack.execution
- attack.stealth
- attack.t1055
logsource:
category: process_creation
product: windows
detection:
selection_parent:
ParentImage|contains:
- \V-SFT
- \VSFT
- \MONITOUCH
selection_child:
Image|endswith:
- \cmd.exe
- \powershell.exe
- \pwsh.exe
- \wscript.exe
- \cscript.exe
- \mshta.exe
- \rundll32.exe
- \regsvr32.exe
- \certutil.exe
- \bitsadmin.exe
condition: selection_parent and selection_child
falsepositives:
- Engineers using a vendor-supplied helper or installer that launches cmd.exe from
the V-SFT directory
- Software updater or setup routines for the Monitouch suite
level: medium
author: Vorant
references:
- https://www.cisa.gov/news-events/ics-advisories/icsa-24-151-02
Behavioural rules are generated from public reporting — validate in your environment before deploying.
Source reporting: https://www.cisa.gov/news-events/ics-advisories/icsa-24-151-02
What this brief leaves out
This page is the free tier: the write-up, the severity, the names. In the app the same report carries its extracted indicators, its detections (Splunk SPL already written, plus Elastic and Microsoft KQL where they apply), the actors and CVEs it names as live profiles, and the vendor research on the same campaign — the primary source the news paraphrased, cited and read directly.
It sits in a corpus of 13,854 reports from 146 sources, 616 of them written in the last seven days, and it grows through the day.
A new account starts with three days of all of it, no card, then keeps the government and CERT reporting free. Name the vendors you run and Slack hears about the reports that touch them — about forty a week that are yours, not the four hundred that are not.
Create a free account What it costs