The use of relative paths in some areas of the code seems to be preventing kadimus from executing if you're not running it from the directory where it's installed. As you can see below, trying to run kadimus from a symlink appears to fail because it's not resolving the full path to errors.txt:
w0rldpain@kali:~$ sudo ln -s /opt/Kadimus/kadimus /usr/local/bin/kadimus
w0rldpain@kali:~$ kadimus -u http://10.10.10.194/news.php?file=statement
_ __ _ _
| |/ /__ _ __| (_)_ __ ___ _ _ ___
| ' // _` |/ _` | | '_ ` _ \| | | / __|
| . \ (_| | (_| | | | | | | | |_| \__ \
|_|\_\__,_|\__,_|_|_| |_| |_|\__,_|___/
v1.5 - LFI Scan & Exploit Tool (@hc0d3r - P0cL4bs Team)
[14:20:11] [INFO] starting scanning the URL: http://10.10.10.194/news.php?file=statement
[14:20:11] [INFO] testing if URL have dynamic content ...
[14:20:11] [INFO] URL dont have dynamic content
[14:20:11] [INFO] analyzing 'file' parameter ...
[14:20:11] [INFO] checking for lfi error messages
[14:20:11] [INFO] using random url: http://10.10.10.194/news.php?file=h2mD6tM
[src/io/utils.c:xfopen:15] fopen(./resource/errors.txt, "r") failed, errno = 2
Could calls like these in the code be modified to use the absolute path to the executable location, so users who want to run kadimus via symlinks or aliases can do so?
The use of relative paths in some areas of the code seems to be preventing kadimus from executing if you're not running it from the directory where it's installed. As you can see below, trying to run kadimus from a symlink appears to fail because it's not resolving the full path to
errors.txt:Could calls like these in the code be modified to use the absolute path to the executable location, so users who want to run kadimus via symlinks or aliases can do so?