Metasploit VS bundler-audit

Metasploit

Metasploit: https://github.com/rapid7/metasploit-framework

1-) Learn Hacking on a debian based distro like Kali Linux - I personally started with tools like nikto, camhacker... and then moved to more complex frameworks like metasploit.

I once had to give a presentation about Metasploit, and whether it was ethically correct for the creator to make it free and open-source, available to everyone. And in researching this I realized that there were a lot of parallels between the arguments for or against hacking tools being readily available and the arguments for or against gun control. I'll just list a few quickly:

Metasploit Framework (mentioned earlier)

This phase is where the pen testers practically prove that there exist potential vulnerabilities in the target system. The pen testers do the hacking using an array of technical approaches and social engineering methods to exploit the vulnerabilities. The ethical hackers commonly use Metasploit framework to automatically execute exploitation against the target systems. Moreover, they may install malwares such as rootkit to persistently maintain their foothold and further compromise the target system.

This Ruby gem is quite useful for detecting versions of gems that are known to be vulnerable to security issues. bundler-audit uses an open database of vulnerable gems called ruby-advisory-db and compares it to the versions that show up in your Gemfile.lock.

bundler-audit - check for known security issues

Let’s take the super famous gem bundler-audit, for instance. It works closely with bundler to provide patch-level verification for your project gems, such as vulnerability checks, insecure gem sources, etc.