Texas Imperial Software WFTPD 3.00 FTP Command CWD memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.8 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in Texas Imperial Software WFTPD 3.00. The impacted element is an unknown function of the component FTP Command Handler. The manipulation of the argument CWD leads to memory corruption. This vulnerability is documented as CVE-2001-0296. Additionally, an exploit exists. It is recommended to apply restrictive firewalling.
Details
A vulnerability, which was classified as very critical, has been found in Texas Imperial Software WFTPD 3.00 (File Transfer Software). This issue affects an unknown functionality of the component FTP Command Handler. The manipulation of the argument CWD with an unknown input leads to a memory corruption vulnerability. Using CWE to declare the problem leads to CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
Buffer overflow in WFTPD Pro 3.00 allows remote attackers to execute arbitrary commands via a long CWD command.
The weakness was released 05/03/2001 as not defined posting (Bugtraq). The advisory is shared at archives.neohapsis.com. The identification of this vulnerability is CVE-2001-0296. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details as well as a public exploit are known. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 10/07/2025).
The exploit is available at exploit-db.com. It is declared as proof-of-concept. The commercial vulnerability scanner Qualys is able to test this issue with plugin 27110 (Potential WFTPD Path/File Mapping Buffer Overflow Vulnerability).
Addressing this vulnerability is possible by firewalling .
The vulnerability is also documented in the databases at Exploit-DB (20794) and Vulnerability Center (SBV-3158†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 10.0VulDB Meta Temp Score: 8.8
VulDB Base Score: 10.0
VulDB Temp Score: 8.8
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Memory corruptionCWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Qualys ID: 🔍
Qualys Name: 🔍
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: FirewallStatus: 🔍
0-Day Time: 🔍
Timeline
05/03/2001 🔍05/03/2001 🔍
07/04/2014 🔍
10/07/2025 🔍
Sources
Advisory: archives.neohapsis.comStatus: Not defined
CVE: CVE-2001-0296 (🔍)
GCVE (CVE): GCVE-0-2001-0296
GCVE (VulDB): GCVE-100-16661
Vulnerability Center: 3158
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 07/04/2014 10:44Updated: 10/07/2025 12:40
Changes: 07/04/2014 10:44 (39), 05/29/2018 10:27 (10), 06/24/2024 07:11 (17), 05/24/2025 10:14 (13), 10/07/2025 12:40 (3)
Complete: 🔍
Cache ID: 216:BE1:103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.