Incident Score: Analysis & Impact (WAZ1766629994)
The details regarding individual company incidents & reports gives you full view from every side.
Rankiteo Score Impact Analysis
Key Highlights From The Incident Analysis
- Timeline of Wazuh'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 Wazuh 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 Wazuh breach identified under incident ID WAZ1766629994.
The analysis begins with a detailed overview of Wazuh's information like the linkedin page: https://www.linkedin.com/company/wazuh, the number of followers: 71485, the industry type: Computer and Network Security and the number of employees: 259 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 754 and after the incident was 753 with a difference of -1 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 Wazuh and their customers.
On 01 February 2025, Wazuh disclosed Botnet Exploitation issues under the banner "Mirai Botnets Exploiting CVE-2025-24016 in Wazuh XDR/SIEM Platform".
Two Mirai botnets are exploiting a critical remote code execution vulnerability (CVE-2025-24016) in the open-source Wazuh XDR/SIEM platform.
The disruption is felt across the environment, affecting Wazuh Manager (versions 4.4.0 - 4.9.0), IoT devices.
In response, and began remediation that includes Upgrade to Wazuh version 4.9.1 or later.
The case underscores how Ongoing, teams are taking away lessons such as Botnet operators rapidly adapt public PoC exploit code to grow or create new botnets. Organizations must prioritize patching critical vulnerabilities promptly to prevent exploitation, and recommending next steps like Upgrade Wazuh Manager to version 4.9.1 or later immediately, Monitor for unusual API access or compromised agents and Implement network segmentation to limit lateral movement.
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 Exploit Public-Facing Application (T1190) with high confidence (95%), with evidence including exploiting a critical remote code execution (RCE) vulnerability (CVE-2025-24016), and affects Wazuh Manager versions 4.4.0 through 4.9.0 and Valid Accounts (T1078) with moderate to high confidence (80%), with evidence including exploitation requires valid Wazuh API credentials, and attackers with API access—either through a compromised dashboard, server cluster, or compromised agent. Under the Execution tactic, the analysis identified Exploitation for Client Execution (T1203) with high confidence (90%), with evidence including unsafe deserialization issue... can be triggered by attackers, and delivering malicious shell scripts that download Mirai malware variants and Command and Scripting Interpreter (T1059) with moderate to high confidence (85%), supported by evidence indicating malicious shell scripts that download Mirai malware variants. Under the Persistence tactic, the analysis identified Server Software Component: Web Shell (T1505.003) with moderate to high confidence (70%), supported by evidence indicating mirai botnets... targeting multiple architectures, including those common in IoT devices. Under the Lateral Movement tactic, the analysis identified Exploitation of Remote Services (T1210) with moderate to high confidence (80%), supported by evidence indicating botnets also scan for legacy vulnerabilities in Hadoop YARN, TP-Link, ZTE, Huawei, and ZyXEL routers. Under the Command and Control tactic, the analysis identified Proxy (T1090) with moderate to high confidence (75%), supported by evidence indicating mirai botnets... expanding their infrastructure. Under the Impact tactic, the analysis identified Resource Hijacking (T1496) with high confidence (90%), with evidence including mirai malware variants targeting multiple architectures, and motivation such as Botnet Expansion. These correlations help security teams understand the attack chain and develop appropriate defensive measures based on the observed tactics and techniques.
Sources & References
- Wazuh Rankiteo Cyber Incident Details: https://www.rankiteo.com/company/wazuh/incident/WAZ1766629994
- Wazuh CyberSecurity Rating page: https://www.rankiteo.com/company/wazuh
- Wazuh Rankiteo Cyber Incident Blog Article: https://blog.rankiteo.com/waz1766629994-vulnerability-june-2025/
- Wazuh CyberSecurity Score History: https://www.rankiteo.com/company/wazuh/history
- Wazuh CyberSecurity Incident Source: https://www.helpnetsecurity.com/2025/06/10/unpatched-wazuh-servers-targeted-by-mirai-botnets-cve-2025-24016/
- Rankiteo A.I CyberSecurity Rating methodology: https://www.rankiteo.com/Images/rankiteo_algo.pdf
- Rankiteo TPRM Scoring methodology: https://static.rankiteo.com/model/rankiteo_tprm_methodology.pdf