Executive Summary

In September 2024, a suspected advanced persistent threat actor tracked as CL-STA-0954 (UNC5820) compromised a telecommunications managed service provider by chaining two Fortinet vulnerabilities. Initial access was gained via CVE-2024-47575 (FortiJump) targeting FortiManager, enabling exfiltration of configurations, private keys, and metadata for over 500 managed FortiGate firewalls. Attackers then exploited CVE-2025-61624, a FortiOS path traversal flaw, to deploy PEERSTITCH—a memory-resident ARM64 implant that injects hooks into legitimate daemons (miglogd and iked) to create a covert inter-process communication bridge, effectively bypassing VPN session security checks without leaving disk artifacts.

This incident signals an accelerating trend of state-linked actors weaponizing centralized network management platforms to compromise downstream infrastructure at scale. The combined use of living-off-the-land injection techniques, WebAssembly payloads, and forensic artifact removal represents a maturation of edge-device malware tradecraft that outpaces conventional endpoint and network detection approaches.

Why This Matters Now

CISA added CVE-2025-61624 to its Known Exploited Vulnerabilities catalog on October 16, 2026, with a federal remediation deadline of October 19, 2026. Organizations relying on FortiOS-managed perimeter infrastructure—particularly telecom and managed service providers—face active exploitation risk. The PEERSTITCH implant's ability to intercept and manipulate VPN sessions without network-visible indicators makes conventional detection inadequate, requiring immediate patching, VPN session integrity validation, and zero-trust segmentation to limit blast radius.

Attack Path Analysis

Related CVEs

MITRE ATT&CK® Techniques

Potential Compliance Exposure

Sector Implications

Sources

Frequently Asked Questions

PEERSTITCH leaves no persistent binary on disk, opens no listening ports, and initiates no outbound network connections. Instead, it injects hooks into two legitimate FortiOS daemons (miglogd and iked) and communicates through inter-process memory, making it invisible to standard endpoint and network monitoring tools.

Cloud Native Security Fabric Mitigations and ControlsCNSF

Based on the attack progression modeled above, these are the defensive controls that would constrain each stage.

This incident demonstrates how a centralized management platform compromise can cascade across hundreds of downstream firewall estates — precisely the scenario Aviatrix Zero Trust CNSF is designed to constrain. By enforcing inline inspection, identity-scoped segmentation, east-west policy controls, and egress filtering, CNSF would likely have reduced the attacker's reachability across managed networks and limited the blast radius of stolen credential material before widespread lateral movement occurred.

Initial Compromise

Control: Cloud Native Security Fabric (CNSF)

Mitigation: Inline IPS carrying CVE-specific signatures for CVE-2024-47575 would likely have detected and flagged the unauthenticated exploit attempt targeting the FortiManager appliance, potentially constraining the attacker's ability to complete initial access before configuration archives were reached.

Privilege Escalation

Control: Zero Trust Segmentation

Mitigation: Zero Trust Segmentation enforcing identity-based, least-privilege access policies between management plane and operational zones would likely have constrained how far stolen credential material could be exercised, reducing the attacker's ability to impersonate privileged administrators across managed devices.

Lateral Movement

Control: East-West Traffic Security

Mitigation: East-west enforcement monitoring workload-to-workload and service-to-service traffic flows would likely have flagged the anomalous inter-device management communications originating from unexpected sources, reducing the attacker's ability to pivot freely across management and operational network zones.

Command & Control

Control: Multicloud Visibility & Control

Mitigation: Centralized traffic observability and behavioral baseline monitoring would likely have flagged the aberrant SSH reverse shell originating from a firewall process, and could have surfaced the anomalous TCP port 8550 activity and link-local addressing patterns as deviations from expected daemon behavior, reducing attacker dwell time.

Exfiltration

Control: Egress Security & Policy Enforcement

Mitigation: Egress policy enforcement with FQDN and IP-based outbound filtering would likely have blocked the bulk data transfer to the unauthorized external destination at 23.240.77[.]233:8085, reducing the attacker's ability to successfully complete exfiltration of the full configuration archive and cryptographic material.

Impact (Mitigations)

Had earlier CNSF controls constrained initial reachability, lateral movement, and exfiltration, the attacker's persistent foothold would likely have been limited to a narrower set of devices rather than spanning the full 500-plus managed firewall estate, meaningfully reducing the scope of downstream client exposure and the attacker's ability to conduct sustained VPN interception and configuration manipulation at scale.

Impact at a Glance

Affected Business Functions

  • Managed Network Operations and VPN Infrastructure
  • Telecommunications Service Delivery and Client Network Management
  • Centralized Firewall and Security Policy Administration
  • Customer Data and Cryptographic Credential Integrity
Operational Disruption

Estimated downtime: 21 days

Financial Impact

Estimated loss: N/A

Data Exposure

Exfiltration of running configuration files and management metadata for more than 500 managed FortiGate firewalls across internal and client networks, including: ciphertext administrative and SSL/VPN credentials, private cryptographic keys and public certificates, internal network topology maps and routing tables, FortiGate serial numbers with associated public IP addresses, and central management SQLite databases. The scope represents a full trust-chain compromise of a telecommunications managed service provider and its downstream enterprise clients, enabling persistent unauthorized VPN sessions, traffic interception, and lateral movement across client environments. Financial loss estimate is set to 0 as no confirmed figure has been publicly disclosed; however, the true financial and reputational exposure is expected to be extremely high given the scale of downstream customer network compromise.

Recommended Actions

  • • Deploy Inline IPS (Suricata) with up-to-date CVE signatures at all network ingress points to detect and block exploitation of known FortiOS/FortiManager vulnerabilities such as CVE-2024-47575 and CVE-2025-61624 before initial compromise can occur.
  • • Enforce Zero Trust Segmentation with identity-based, least-privilege policies between management plane components and operational firewall networks, preventing stolen credentials and trust material from being used to pivot across enrolled managed devices or impersonate centralized management platforms.
  • • Implement East-West Traffic Security monitoring on all inter-appliance and service-to-service flows, establishing behavioral baselines that alert on anomalous management protocol usage, unexpected VPN session establishment patterns, and lateral movement across network segments.
  • • Apply Egress Security and Policy Enforcement with strict FQDN and IP-based outbound filtering to block unauthorized data transfer to external destinations and intercept reverse shell callback traffic, preventing both bulk configuration exfiltration and C2 channel establishment through cloud firewall (ACF) controls.
  • • Activate Multicloud Visibility and Control with centralized traffic observability and continuous anomaly detection across all hybrid and edge network components, ensuring that covert inter-process communication bridges, daemon memory injection artifacts, and logging disruption events are surfaced and trigger automated incident response workflows aligned with NIST.800-53.AU-6 and NIST.CSF.DE.CM-7.

Secure the Paths Between Cloud Workloads

A cloud-native security fabric that enforces Zero Trust across workload communication—reducing attack paths, compliance risk, and operational complexity.

Cta pattren Image