Firestarter Backdoor Persisted on Cisco Firewalls Despite Patches, Agencies Warn

· Original article ↗

Summary

U.S. and U.K. agencies identified Firestarter, a backdoor that can persist on Cisco firewalls after patches and standard reboots. CISA found it on a federal device and ordered agencies to audit appliances and submit memory snapshots.

Key points

  • CISA said it found Firestarter on a U.S. federal agency’s Cisco Firepower device; U.S. and U.K. authorities published a malware analysis report.
  • Cisco Talos attributed Firestarter to UAT-4356 and linked the actor to the earlier ArcaneDoor campaign.
  • Firestarter manipulates the Service Platform mount list to restore itself after reboots and injects shellcode into LINA to intercept VPN authentication requests containing a trigger sequence.
  • UAT-4356 exploited CVE-2025-20333 and CVE-2025-20362 for initial access; patching those vulnerabilities did not remove implants already on affected devices.
  • In the analyzed federal incident, attackers used Line Viper to access configurations, credentials and encryption keys, then later used Firestarter to redeploy Line Viper.
  • CISA ordered federal civilian agencies to audit Cisco firewall infrastructure and submit memory snapshots. Cisco recommends reimaging suspected devices and has released updated software.

Article Details

Attack Vectors
  • UAT-4356 exploited CVE-2025-20333, a remote code execution flaw in the VPN web server component, and CVE-2025-20362, an unauthorized access vulnerability, to gain initial access to Cisco devices.
  • The attackers deployed Line Viper to access device configurations, credentials, and encryption keys, then installed Firestarter.
  • Firestarter injects shellcode into LINA, intercepts VPN authentication requests, and executes attacker-supplied code when a request contains a hidden trigger sequence.
  • Firestarter rewrites the Cisco Service Platform mount list and copies itself to a secondary location so it can relaunch after software updates and standard reboots.
Defensive Notes
  • Cisco released updated software to address the persistence mechanism, but recommends reimaging devices when compromise is suspected.
  • According to CISA and Cisco, a hard reboot—physically disconnecting the device from power—is required to clear the persistence mechanism from memory; a standard software reboot is insufficient.
  • CISA's emergency directive required federal civilian agencies to audit Cisco firewall infrastructure and submit device memory snapshots for analysis.
  • Cisco advises customers needing assistance to contact Cisco Technical Assistance.

MITRE ATT&CK

CVE

Threat Actors

Malware

Vendors

Products

Countries

Industries

Related Articles