i-Ftp 2.20 Schedule.xml Time stack-based overflow

Summaryinfo

A vulnerability was found in i-Ftp 2.20. It has been rated as critical. The impacted element is an unknown function of the file Schedule.xml. Performing a manipulation of the argument Time results in stack-based overflow. This vulnerability is cataloged as CVE-2014-125114. It is possible to initiate the attack remotely. Furthermore, there is an exploit available.

Detailsinfo

A vulnerability classified as critical has been found in i-Ftp 2.20. This affects an unknown function of the file Schedule.xml. The manipulation of the argument Time with an unknown input leads to a stack-based overflow vulnerability. CWE is classifying the issue as CWE-121. A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function). This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

A stack-based buffer overflow vulnerability exists in i-Ftp version 2.20 due to improper handling of the Time attribute within Schedule.xml. By placing a specially crafted Schedule.xml file in the i-Ftp application directory, a remote attacker can trigger a buffer overflow during scheduled download parsing, potentially leading to arbitrary code execution or a crash.

The weakness was shared by metacom. The advisory is shared at raw.githubusercontent.com. This vulnerability is uniquely identified as CVE-2014-125114 since 07/24/2025. The exploitability is told to be easy. It is possible to initiate the attack remotely. Technical details and a public exploit are known.

The exploit is shared for download at exploit-db.com. It is declared as proof-of-concept. By approaching the search of inurl:Schedule.xml it is possible to find vulnerable targets with Google Hacking.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the vulnerability database at Exploit-DB (35177). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

• i-Ftp

Version

• 2.20

CPE 2.3info

• 🔒

CPE 2.2info

• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion