Executive SummaryRisk level: High
What happened

The Gunra ransomware gang is exploiting known vulnerabilities in Fortinet products to bypass multi-factor authentication (MFA), effectively gaining access to critical systems.

Who is affected

Critical infrastructure organizations utilizing Fortinet firewall and VPN solutions are particularly vulnerable to these attacks.

Why it matters

These vulnerabilities can lead to severe operational disruptions, data breaches, and financial losses, highlighting the need for robust security measures.

Immediate recommended actions

  • Conduct an immediate assessment of all Fortinet devices in your environment.
  • Implement strict monitoring and alerting for unusual authentication attempts.
  • Review and update incident response plans to address potential ransomware incidents.
  • Validate MFA configurations and ensure no loopholes exist.

Key Technical Findings

Vulnerability / Campaign Type

Exploitation of Fortinet vulnerabilities leading to MFA bypass.

Affected Systems

Fortinet firewalls and VPN appliances, versions not specified in the source material.

Initial Access Vector

Exploitation of known vulnerabilities in network appliances.

Execution Method

Execution of custom payloads derived from leaked Conti ransomware code.

Persistence

Potential use of backdoors or web shells installed through initial compromise.

Privilege Escalation

Not specified in the source material.

Defense Evasion

Utilization of anti-forensic techniques to hide malicious activity.

Credential Access

Bypassing MFA mechanisms to gain unauthorized access.

Lateral Movement

Not specified in the source material.

Data Exfiltration

Not specified in the source material.

Impact Level

High impact on organizational operations and data integrity.

Technical Background

The Gunra ransomware operation employs a sophisticated approach by leveraging vulnerabilities present in Fortinet appliances, specifically within their firewall and VPN solutions. These vulnerabilities typically relate to outdated software or misconfigurations that attackers can exploit to bypass security measures such as MFA. The leak of Conti’s source code has further empowered adversaries, enabling them to adapt existing attack vectors for their purposes, increasing the risk to numerous organizations relying on these systems.

Organizations are at heightened risk as many still utilize legacy versions of Fortinet products that may not have received timely updates or patches. The primary goal of these attackers is often to encrypt critical data for ransom while simultaneously extracting sensitive information, thus maximizing their leverage over targeted entities. Security controls such as robust MFA configurations and regular vulnerability assessments are essential in mitigating these risks.

Attack Chain Analysis

  1. Initial Access

    ActivityExploitation of known vulnerabilities in Fortinet devices.

    EvidenceLog entries showing unauthorized access attempts or exploitation indicators.

    TelemetryNetwork logs capturing incoming requests to vulnerable endpoints.

    Detection opportunityMonitoring for unusual authentication patterns or failed access attempts.

  2. Execution

    ActivityDeployment of ransomware payloads using compromised credentials.

    EvidenceFile system changes corresponding with known ransomware behavior.

    TelemetryProcess execution logs indicating suspicious processes initiated by exploited services.

    Detection opportunityUse of endpoint detection tools to capture anomalous behaviors during payload execution.

Deep Technical Behavior Analysis

The Gunra ransomware demonstrates a range of behaviors that make it particularly challenging to detect once initial access is achieved. Common tactics include creating persistence mechanisms through scheduled tasks or registry modifications that remain undetected until triggered. Furthermore, the use of encryption algorithms designed to obfuscate the data being exfiltrated can complicate forensic analysis post-incident. The payloads might also employ anti-detection strategies that evade traditional security tools by mimicking legitimate application behavior, thus avoiding immediate detection by security monitoring solutions.

This behavior necessitates a multi-layered defensive strategy that not only focuses on traditional perimeter defenses but also on internal monitoring and anomaly detection throughout the environment. Regularly updating detection rules to adapt to evolving tactics used by ransomware groups is crucial in maintaining an effective defense posture against such sophisticated threats.

Indicators of Compromise

No indicators of compromise were provided in the source material.

Indicators of Behavior

Behavioral Indicator Description Data Source Confidence
MFA Bypass Attempts Multiple failed MFA attempts followed by successful access. MFA logs, EDR alerts Potential
Anomalous Process Execution Execution of processes that deviate from normal operating patterns. EDR telemetry, Sysmon logs Potential

Detection Engineering Guidance

T1070 — Indicator Removal on Host
  • ObjectiveDetect attempts to remove traces of unauthorized activity.
  • Suspicious patternFrequent deletion of logs or artifacts post-exploitation.
  • Data sourceFile system logs, EDR logs.
  • False positivesRoutine maintenance activities may trigger alerts.
  • ResponseAnalyze the context of deletion events before escalating.
index=edr (event_type='delete' OR event_type='modify') user!=system | stats count by user, file_path | where count > 10
T1555 — Credentials from Password Stores
  • ObjectiveIdentify unauthorized access to stored credentials.
  • Suspicious patternAccessing password databases without appropriate context.
  • Data sourcePassword manager logs, EDR alerts.
  • False positivesLegitimate administrative access may trigger alerts.
  • ResponseInvestigate context around access attempts for legitimacy.
index=edr process='credential_manager' | stats count by user | where count > 5