Tagger LE Tags.PHP Remote File Include Vulnerability
BID:19464
Info
Tagger LE Tags.PHP Remote File Include Vulnerability
| Bugtraq ID: | 19464 |
| Class: | Input Validation Error |
| CVE: | |
| Remote: | Yes |
| Local: | No |
| Published: | Aug 10 2006 12:00AM |
| Updated: | Aug 11 2006 04:50PM |
| Credit: | Morgan is credited with the discovery of this vulnerability. |
| Vulnerable: |
Venture Nine Tagger LE 3 |
| Not Vulnerable: | |
Discussion
Tagger LE Tags.PHP Remote File Include Vulnerability
Tagger LE is prone to a remote file-include vulnerability because it fails to properly sanitize user-supplied input.
An attacker can exploit this issue to include an arbitrary remote file containing malicious PHP code and execute it in the context of the webserver process. This may facilitate a compromise of the application and the underlying system; other attacks are also possible.
This issue affects version 3; other versions may also be vulnerable.
Tagger LE is prone to a remote file-include vulnerability because it fails to properly sanitize user-supplied input.
An attacker can exploit this issue to include an arbitrary remote file containing malicious PHP code and execute it in the context of the webserver process. This may facilitate a compromise of the application and the underlying system; other attacks are also possible.
This issue affects version 3; other versions may also be vulnerable.
Exploit / POC
Tagger LE Tags.PHP Remote File Include Vulnerability
Attackers can exploit this issue via a web client.
The following proof-of-concept URI is available:
Attackers can exploit this issue via a web client.
The following proof-of-concept URI is available:
Solution / Fix
Tagger LE Tags.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]:[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]:[email protected].