HTTP Commander Path Disclosure Vulnerability
BID:8949
Info
HTTP Commander Path Disclosure Vulnerability
| Bugtraq ID: | 8949 |
| Class: | Input Validation Error |
| CVE: | |
| Remote: | Yes |
| Local: | No |
| Published: | Nov 01 2003 12:00AM |
| Updated: | Nov 01 2003 12:00AM |
| Credit: | The disclosure of this issue has been credited to Zero_X <[email protected]>. |
| Vulnerable: |
HTTP Commander HTTP Commander 4.0 |
| Not Vulnerable: | |
Discussion
HTTP Commander Path Disclosure Vulnerability
HTTP Commander is reported to be prone to path disclosure issue in the 'file' parameter that may lead to an attacker gaining sensitive information about the installation path of the system.
Information gained by exploiting this attack may aid an attacker in launching further attacks against a vulnerable system.
HTTP Commander version 4.0 is reported to be prone to this issue, however other versions may be affected as well.
HTTP Commander is reported to be prone to path disclosure issue in the 'file' parameter that may lead to an attacker gaining sensitive information about the installation path of the system.
Information gained by exploiting this attack may aid an attacker in launching further attacks against a vulnerable system.
HTTP Commander version 4.0 is reported to be prone to this issue, however other versions may be affected as well.
Exploit / POC
HTTP Commander Path Disclosure Vulnerability
The following proof of concept has been provided:
http://www.example.com/NetDemo2/html.aspx?file=.
you will read the message:
Access to the path "C:\WEBHOSTING4LIFE ASPNET\SERGANT\GUEST" is denied.
The following proof of concept has been provided:
http://www.example.com/NetDemo2/html.aspx?file=.
you will read the message:
Access to the path "C:\WEBHOSTING4LIFE ASPNET\SERGANT\GUEST" is denied.
Solution / Fix
HTTP Commander Path Disclosure Vulnerability
Solution:
Currently we are not aware of any vendor-supplied patches for this issue. If you feel we are in error or are aware of more recent information, please mail us at: [email protected] <mailto:[email protected]>.
Solution:
Currently we are not aware of any vendor-supplied patches for this issue. If you feel we are in error or are aware of more recent information, please mail us at: [email protected] <mailto:[email protected]>.