Having myself participated in the private beta of the website and I have been involved with the creation of the room, I invite you into taking a journey to discover how to implement AttackerKB in the best way possible into your workflow and how you will gain from it.
What is AttackerKB?
Before telling you how, I need to show you why you would want AKB to be part of your daily life. In order to do so we will cover what it does.
AttackerKB - not all vulns are created equal.
This slogan says it all, AttackerKB is a tool on which you can search vulnerabilities which are all rated thanks to assessments performed by the community.
Here are key points:
- Is community based
- In constant development and improvement
- Up-to-date CVE database
- CVEs assesments and ratings are provided by other users such as pentesters, researchers...
After going to https://attackerkb.com/ you have access to the most active and popular CVEs, but you can also search one using the search bar using its code (CVE-XXXX-XXXX) or key words, or the product/system related to the vulnerabilty.
But what makes AKB a really powerful tool is the diversity and relevance of the information provided on each CVE on their respective pages.
From assessments made about it, to a rating system with information such as the Attacker Value and Exploitability.
You can also find -if there is one- the metasploit modules, MITRE ratings, lots of resources/references where the CVE has been mentioned on other websites.
You will also find on some CVE an official Rapid7 Analysis such as the following one.
But wait, there is more!
You have a scoreboard system with users score, to get point you need to make assessments or reply to one and the more people upvote your assessment/comment the more points you score!
This goes along with cool badges:
Okay okay, now, how do I make the best out of AKB?
At this point you must already have a pretty good idea on how to do that and I will try to cover the matter as fast as possible.
After enumeration, I would recommend searching terms on AKB such as services names and versions. After some more googling if you find a CVE online that seems to it your case, search for it on AKB, a lot of useful CVEs are not well documented out there or these documentations/blog articles are hard to find.
This is what AKB is for!
I have also made a tool called AttackerKB-Explorer which provides a basic CLI (Command-Line Interface) to AttackerKB using their API.
(Note: It's not always up-to-date and well maintained)