Rankiteo Logo
Rankiteo
Leader in Cyber Underwriting
Loading...
NEWRankiteo Cyber Underwriting Desktop - Score, price, and bind from your desktop
WindowsmacOSLinux
Download
Analyze » Mitsubishi Electric » MIT1770021852

Incident Score: Analysis & Impact (MIT1770021852)

The details regarding individual company incidents & reports gives you full view from every side.

Rankiteo Score Impact Analysis

Rankiteo Incident Impact-4
Company Score Before Incident748 / 1000
Company Score After Incident744 / 1000
Company LinkView Mitsubishi Electric Profile
INCIDENT NUMBERMIT1770021852
Type of Cyber IncidentVulnerability
ATTACK VECTORLocal Access
DATA EXPOSEDNA
INCIDENT DATE30/01/2026
STATUSVulnerability identified and disclosed

Key Highlights From The Incident Analysis

  • Timeline of Mitsubishi Electric's Vulnerability and lateral movement inside company's environment.
  • Overview of affected data sets, including SSNs and PHI, and why they materially increase incident severity.
  • How Rankiteo’s incident engine converts technical details into a normalized incident score.
  • How this cyber incident impacts Mitsubishi Electric Rankiteo cyber scoring and cyber rating.
  • Rankiteo’s MITRE ATT&CK correlation analysis for this incident, with associated confidence level.

Full Incident Analysis Transcript

In this Rankiteo incident briefing, we review the Mitsubishi Electric breach identified under incident ID MIT1770021852.

The analysis begins with a detailed overview of Mitsubishi Electric's information like the linkedin page: https://www.linkedin.com/company/mitsubishielectric, the number of followers: 289900, the industry type: Appliances, Electrical, and Electronics Manufacturing and the number of employees: 6644 employees

After the initial compromise, the video explains how Rankiteo's incident engine converts technical details into a normalized incident score. The incident score before the incident was 748 and after the incident was 744 with a difference of -4 which is could be a good indicator of the severity and impact of the incident.

In the next step of the video, we will analyze in more details the incident and the impact it had on Mitsubishi Electric and their customers.

On 01 January 2024, Mitsubishi Electric disclosed Denial-of-Service (DoS) issues under the banner "Medium-Severity Vulnerability in Iconics Suite SCADA Systems Exposes Critical Infrastructure to DoS Attacks".

A medium-severity vulnerability (CVE-2025-0921) in Mitsubishi Electric’s Iconics Suite SCADA system has been identified, enabling attackers to trigger denial-of-service (DoS) conditions on industrial control systems (ICS).

The disruption is felt across the environment, affecting GENESIS64, MC Works64, GENESIS version 11.00.

In response, and began remediation that includes Patches released for GENESIS version 11.01 and later; mitigations recommended for MC Works64.

The case underscores how Vulnerability identified and disclosed, and recommending next steps like Apply patches for GENESIS version 11.01 and later; implement mitigations for MC Works64; ensure proper directory permissions to prevent exploitation of CVE-2024-7587.

Finally, we try to match the incident with the MITRE ATT&CK framework to see if there is any correlation between the incident and the MITRE ATT&CK framework.

The MITRE ATT&CK framework is a knowledge base of techniques and sub-techniques that are used to describe the tactics and procedures of cyber adversaries. It is a powerful tool for understanding the threat landscape and for developing effective defense strategies.

MITRE ATT&CK® Correlation Analysis

Rankiteo's analysis has identified several MITRE ATT&CK tactics and techniques associated with this incident, each with varying levels of confidence based on available evidence. Under the Initial Access tactic, the analysis identified Exploitation of Remote Services (T1210) with moderate confidence (60%), supported by evidence indicating vulnerability (CVE-2025-0921) in Mitsubishi Electric’s Iconics Suite SCADA system and Valid Accounts (T1078) with moderate confidence (50%), supported by evidence indicating attackers with local access to manipulate the SMSLogFile path. Under the Privilege Escalation tactic, the analysis identified Exploitation for Privilege Escalation (T1068) with moderate to high confidence (70%), supported by evidence indicating execution-with-unnecessary-privileges weakness in the Pager Agent component and Abuse Elevation Control Mechanism: Bypass User Account Control (T1548.002) with moderate confidence (50%), supported by evidence indicating cVE-2024-7587 granting excessive permissions to C such as \ProgramData\ICONICS. Under the Impact tactic, the analysis identified Endpoint Denial of Service (T1499) with high confidence (90%), supported by evidence indicating trigger denial-of-service (DoS) conditions on industrial control systems (ICS) and Endpoint Denial of Service: Service Exhaustion Flood (T1499.002) with moderate to high confidence (80%), supported by evidence indicating corrupted driver forces an endless repair loop, rendering OT workstations inoperable. Under the Defense Evasion tactic, the analysis identified Impair Defenses: Disable or Modify Tools (T1562.001) with moderate to high confidence (70%), supported by evidence indicating overwrite critical system drivers like cng.sys to force an endless repair loop. These correlations help security teams understand the attack chain and develop appropriate defensive measures based on the observed tactics and techniques.

Initial Access
Exploitation of Remote Services (60%)
Valid Accounts (50%)
Privilege Escalation
Exploitation for Privilege Escalation (70%)
Abuse Elevation Control Mechanism: Bypass User Account Control (50%)
Impact
Endpoint Denial of Service (90%)
Endpoint Denial of Service: Service Exhaustion Flood (80%)
Defense Evasion
Impair Defenses: Disable or Modify Tools (70%)

Sources & References