Loading vulnerability…
CVE-2024-20358 is a command injection vulnerability in the Cisco Adaptive Security Appliance (ASA) restore functionality available in Cisco ASA Software and Cisco Firepower Threat Defense (FTD) Software. Backup file contents are improperly sanitized during restoration. An authenticated local attacker with administrator-level privileges can restore a crafted backup file to execute arbitrary commands on the underlying Linux operating system as root.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
12 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A previously disclosed high-severity vulnerability in Cisco ASA and FTD products mentioned as part of Cisco's security history; no specific technical details are provided in the content.
A Cisco ASA/FTD vulnerability from the ArcaneDoor campaign that was observed used by a threat actor; the content indicates two of the vulnerabilities were exploited for privilege escalation and persistence, but does not unambiguously map which two by CVE.
A Cisco ASA/FTD zero-day vulnerability identified during the ArcaneDoor investigation; the content states only CVE-2024-20353 and CVE-2024-20359 were exploited in the campaign.
A zero-day vulnerability affecting Cisco ASA and FTD software, identified during the ArcaneDoor investigation. The executive summary explicitly excludes it from campaign exploitation, although a later paragraph inconsistently describes all three vulnerabilities as exploited. Its technical mechanism is not described.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.