Misconfig Mapper is a fast tool to help you uncover security misconfigurations on popular third-party services used by your company and/or bug bounty targets!
Assuming you keep the binary in a directory that is in your path, or you make a link in your path so that you can run it from anywhere on the filesystem. As it is now, the templates folder is created and the services.json is downloaded in every location you run the program from. This pr fixes that and ./templates/services.json is always kept where the binary is. Example follows:
I can run misconfig-mapper from any bounty location, however a new ./templates/services.json gets created in each one. With the fixes above, the program always looks for ./templates/services.json in the actual binary location so that would be /root/Tools/misconfig-mapper/templates/services.json. Sames goes for updates.
Assuming you keep the binary in a directory that is in your path, or you make a link in your path so that you can run it from anywhere on the filesystem. As it is now, the templates folder is created and the services.json is downloaded in every location you run the program from. This pr fixes that and
./templates/services.json
is always kept where the binary is. Example follows:Binary location:
Workplace directory structure:
I can run
misconfig-mapper
from any bounty location, however a new./templates/services.json
gets created in each one. With the fixes above, the program always looks for./templates/services.json
in the actual binary location so that would be/root/Tools/misconfig-mapper/templates/services.json
. Sames goes for updates.