CVE-2023-32560 is a critical buffer overflow vulnerability affecting Ivanti Avalanche Manager, specifically the Wavelink Avalanche Manager component. An attacker can send a specially crafted message to the service and trigger memory corruption, resulting in a crash or arbitrary code execution. Available reporting describes this issue collectively as critical Avalanche buffer overflows fixed by Ivanti, but does not provide sufficient technical detail to identify the exact vulnerable function or whether the flaw is strictly stack-based, heap-based, or spans multiple code paths. Ivanti fixed the issue in Avalanche version 6.4.1.
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.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos (1 hidden).
This repository contains a single Metasploit module (Ruby file) that exploits a stack buffer overflow vulnerability (CVE-2023-32560) in Ivanti Avalanche MDM versions prior to 6.4.1, specifically tested on v6.4.0.0 running on Windows 10. The exploit targets the Avalanche Manager service, which listens by default on TCP port 1777. By sending a specially crafted message containing a custom ROP chain and a Metasploit payload, the attacker can achieve arbitrary code execution as NT AUTHORITY\SYSTEM. The module includes a check method to verify if the service is present and vulnerable, and the exploit method constructs and sends the malicious packet. The payload is customizable via Metasploit, and the exploit is operational, providing SYSTEM-level access if successful. The only fingerprintable endpoint is the TCP service on port 1777. The code is well-structured and leverages Metasploit's Remote::Tcp mixin for network communication.
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.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.