-
Notifications
You must be signed in to change notification settings - Fork 14.4k
Why CVE is not available
Caitlin Condon edited this page Dec 11, 2018
·
2 revisions
This documentation explains why sometimes you might see this message in either msfconsole or module documentation:
CVE: Not available
This message indicates that, as far as the Metasploit team knows, there is no CVE assigned to that particular module at the moment. There are multiple reasons why this might happen:
- The vendor does not wish to assign a CVE.
- There is a delay in the process of assigning a CVE.
- The module is not meant to target a specific CVE. Likely something generic.
- We are unable to find a matching CVE because there isn't enough technical information to verify.
The Metasploit team will continue to monitor existing modules without any CVEs, and update them as needed.
If you believe the module's CVE information is inaccurate or out-of-date, please feel free to submit a pull request to us. Thank you! :-)
- Home Welcome to Metasploit!
- Using Metasploit A collection of useful links for penetration testers.
-
Setting Up a Metasploit Development Environment From
apt-get install
togit push
. - CONTRIBUTING.md What should your contributions look like?
- Landing Pull Requests Working with other people's contributions.
- Using Git All about Git and GitHub.
- Contributing to Metasploit Be a part of our open source community.
- Meterpreter All about the Meterpreter payload.