Loading vulnerability…
AASync version 2.2.1.0 contains a stack-based buffer overflow vulnerability (CWE-121). The vulnerability arises due to improper bounds checking when handling user-supplied input, leading to the possibility of overwriting stack memory.
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.
This repository contains a single Metasploit exploit module targeting a stack buffer overflow vulnerability in AASync v2.2.1.0 (Win32), specifically when the client processes a response to the FTP LIST command. The exploit works by running a malicious FTP server that, upon receiving a LIST command from the vulnerable client, sends a specially crafted directory listing. This listing contains a filename ('admin passwords.txt') followed by a large buffer that overflows the stack, overwriting the Structured Exception Handler (SEH) and allowing execution of arbitrary code (Metasploit payload). The exploit is designed for Windows XP SP3 Universal and references CVE-2019-5619. The only file in the repository is a Ruby script compatible with the Metasploit framework, and it leverages Metasploit's payload system to deliver shellcode to the target. The attack vector is network-based, requiring the victim to connect to the attacker's FTP server. The main fingerprintable endpoint is the crafted filename used in the malicious directory listing.
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.
1 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.