Loading vulnerability…
CVE-2014-125114 is a stack-based buffer overflow in i-Ftp version 2.20. The flaw is caused by improper handling of the Time attribute in Schedule.xml during scheduled download parsing. If a specially crafted Schedule.xml file is placed in the i-Ftp application directory, the application can copy or process attacker-controlled Time attribute data into a fixed-size stack buffer without adequate bounds checking, resulting in memory corruption. Successful exploitation may allow arbitrary code execution in the context of the affected process, or may cause the application to crash.
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 module (modules/exploits/windows/fileformat/iftp_schedule_bof.rb) that exploits a stack-based buffer overflow vulnerability in i-FTP v2.20 (CVE-2014-125114). The exploit works by generating a specially crafted Schedule.xml file with an overly long 'Time' attribute in an 'Event' element. When this file is placed in the i-FTP folder and processed by the application (tested on Windows XP SP3), it triggers a buffer overflow, allowing arbitrary code execution with the privileges of the i-FTP process. The module allows the attacker to specify a custom payload, which is injected into the file. The attack vector is local, as it requires the victim to open or process the malicious file. The only fingerprintable endpoint is the Schedule.xml file itself. The repository is structured as a standard Metasploit exploit module, with all logic contained in a single Ruby file.
5 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.