HighPublic exploit

Stack Buffer Overflow in WinaXe FTP Client 7.7 FTP Banner Parsing

IdentifiersCVE-2025-34107CWE-121· Stack-based Buffer Overflow

CVE-2025-34107 is a stack-based buffer overflow in WinaXe FTP Client version 7.7. The flaw is in the FTP banner parsing functionality implemented in WCMDPA10.dll. When the client connects to a remote FTP server, it processes the server banner, including the initial '220 Server Ready' response. A malicious or malformed FTP server can return an overly long 220 response that overflows a stack buffer in the banner parsing routine, potentially allowing arbitrary code execution in the security context of the user running the client.

For your environment

Are you exposed to this one?

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.

Start free trial

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can result in arbitrary code execution on the client system with the privileges of the logged-in user running WinaXe FTP Client. In practice, this could allow an attacker operating a malicious FTP server, or positioned to tamper with FTP traffic, to execute attacker-controlled code, compromise the client host, access or modify user data, install malware, or use the foothold for further post-exploitation activity subject to the user's privileges.

Mitigation

If you can’t patch tonight, do this now.

Do not connect WinaXe FTP Client 7.7 to untrusted or Internet-exposed FTP servers. Restrict outbound FTP connections to trusted servers only, preferably through network allowlisting. Where possible, inspect or proxy FTP traffic to block anomalously long server banners. Run the client with least privilege and use host-based exploit mitigations such as DEP, ASLR, and endpoint protection to reduce exploitation reliability and impact. Network segmentation and application control can further limit post-compromise effects.

Remediation

Patch, then assume compromise.

Upgrade to a vendor-fixed version if one is available. If no patched release is available, discontinue use of WinaXe FTP Client 7.7 in untrusted environments and replace it with a supported FTP client that safely handles server banner parsing. The vulnerable banner parsing logic in WCMDPA10.dll should be corrected by enforcing strict bounds checking on the 220 response before copying or processing it, and by using memory-safe string handling routines.

PUBLIC EXPLOITS

Exploits

1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.

VALID 1 / 1 TOTALView more in app

winaxe_server_ready.rbMaturityWeaponizedFrameworkmetasploitVerified exploit

This repository contains a single Metasploit module (modules/exploits/windows/ftp/winaxe_server_ready.rb) that exploits a buffer overflow vulnerability in the WinaXe 7.7 FTP client (CVE-2025-34107). The exploit works by running a malicious FTP server that, upon connection from a vulnerable client, sends a specially crafted '220 Server Ready' response containing a buffer overflow payload. This payload can be customized using any Metasploit-compatible payload (e.g., reverse shell, meterpreter). The exploit targets Windows systems running the WinaXe 7.7 FTP client. The code is written in Ruby and leverages the Metasploit framework's FTP server mixin. The main entry point is the on_client_connect function, which handles the delivery of the exploit when a client connects. No hardcoded IPs, domains, or file paths are present; the fingerprintable endpoint is the FTP server itself, which must be accessible to the victim client.

Disclosed Nov 3, 2016rubynetwork

ACTIVITY FEED

Recent activity

2 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.

2 SOURCESView more in app

No news coverage yet. Advisories and community discussion only.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.

Start free trial

Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity2