SmartFTP Banner Remote Heap Buffer Overflow Vulnerability
BID:22390
Info
SmartFTP Banner Remote Heap Buffer Overflow Vulnerability
| Bugtraq ID: | 22390 |
| Class: | Boundary Condition Error |
| CVE: |
CVE-2007-0790 |
| Remote: | Yes |
| Local: | No |
| Published: | Feb 05 2007 12:00AM |
| Updated: | May 12 2015 07:34PM |
| Credit: | Marsu Pilami is credited with discovering this issue. |
| Vulnerable: |
SmartFTP SmartFTP 2.0.1002 |
| Not Vulnerable: | |
Discussion
SmartFTP Banner Remote Heap Buffer Overflow Vulnerability
SmartFTP is prone to a remote heap-based buffer-overflow vulnerability because the application fails to properly bounds-check user-supplied data prior to copying it to an insufficiently sized memory buffer.
Exploiting this issue allows remote attackers to execute arbitrary machine code in the context of the server application, facilitating the compromise of affected computers.
SmartFTP version 2.0.1002 is reported vulnerable; other versions may also be affected.
SmartFTP is prone to a remote heap-based buffer-overflow vulnerability because the application fails to properly bounds-check user-supplied data prior to copying it to an insufficiently sized memory buffer.
Exploiting this issue allows remote attackers to execute arbitrary machine code in the context of the server application, facilitating the compromise of affected computers.
SmartFTP version 2.0.1002 is reported vulnerable; other versions may also be affected.
Exploit / POC
SmartFTP Banner Remote Heap Buffer Overflow Vulnerability
An attacker may exploit this issue by crafting a malicious banner reply on an FTP site.
An attacker may exploit this issue by crafting a malicious banner reply on an FTP site.
Solution / Fix
SmartFTP Banner Remote Heap Buffer Overflow Vulnerability
Solution:
Currently we are not aware of any vendor-supplied patches for this issue. If you feel we are in error or if you are aware of more recent information, please mail us at: [email protected].
Solution:
Currently we are not aware of any vendor-supplied patches for this issue. If you feel we are in error or if you are aware of more recent information, please mail us at: [email protected].