There’s thousand of vulnerabilities, but do you ever struggle work out what ones might actually be useful to you if you are defending or attacking?
Well don’t worry I’ve started to document some things that might help you both attack and defend in CYBERSPACE!
Now this is a snipped of what I’m working on, but I wanted to at least start the ball rolling. If you have any of these in your environment you probably want to be getting them bumped up the priority list ASAP.
This is just the start, I’m going to look at how we can do more with this:
Hopefully this gives some idea that even though there are thousands of vulns, and over 700 in CISA KEV, you might find some need more attention than others!
The CVSS score of a vuln is one thing, knowing if there is a public exploit, a private one and how much of a target it is for exploit developes, nation states and cybercriminals helps guide this.
Criteria for Offensive KEV
The way I’m looking at this is:
- Is a public exploit available?
- Is the product in question largely deploed globally?
- Is this RCE or Privesc?
- How old is it?
- Is the exploit “probably” useful for an attacker?
if it’s NOT on my list it doesn’t mean don’t remediate, patch, mitigate ect. I’m just looking at this from a pentesters perspective to try and work out what I probably can leverage vs it existing.
Latest Update – 09-08-2022
So far we have now added in:
- Metasploit modules where there is a CVE referenced.
- Nuclei templates
- Manual additions where a public POC is mentioned
- Manual Limited assessment of data to see if the vuln would likely be useful for a pentestration test