Running cvemap
Learn about running cvemap with examples including commands and output
For all of the flags and options available for cvemap
be sure to check out the Usage page. On this page we’ll share examples running cvemap
with specific flags and goals
and the output you can expect from each.
If you have questions, reach out to us through Help.
Prerequisites for cvemap
Before using cvemap, you’ll need to get a ProjectDiscovery Cloud Platform (PDCP) account and API key so that you can access the cvemap API data.
Sign up for PDCP
Navigate to https://cloud.projectdiscovery.io/ and click “Sign Up” (or “Sign In” if you already have a PDCP account).
Get your PDCP API Key
Once signed into ProjectDiscovery Cloud Platform, you can navigate to https://cloud.projectdiscovery.io/?ref=api_key to find your API Key.
Use the copy button to copy your API Key - we nee dthis to authenticate your install
Authorize cvemap with PDCP
To authenticate your install of cvemap, run
When prompted, paste the key you obtained above.
Basic Examples
By default, cvemap
lists all the known exploited vulnerabilities based CVEs published by cisa.
List top known exploited vulnerabilities
List top CVEs on HackerOne
List top CVEs being reported on hackerone platform using -h1
or -hackerone
option.
cvemap provide multiple ways to query cve data i.e by product
, vendor
, severity
, cpe
, assignee
, cvss-score
, epss-score
, age
etc, for example:
List all CVEs for Confluence
List all the cves published for Atlassian Confluence:
As default, cvemap display default / limit fields which can be custizmed and controoled using -field
/ -f
option, for example:
To list cves with matching threshold like, CVSS score or EPSS Score / Percentile, below options can be used:
To filter cves to match with specifc conditions like, cves has public poc or template and in the list of kev, belows options can beused:
Return CVE IDs only
To return only CVE IDs, -lsi
or -list-id
flag can be used along with existing filter or search of cvemap.
JSON Output
Advanced Filters
You can combine filters with a -q
query to match multiple filters. For example:
You can see the documentation for all available filters below:
Metadata
Age of the CVE
The assignee for this CVE.
Typically this is an email address such as security@apache.org
or cve@mitre.org
The description of the CVE from the NVD
The CVE ID for a specific CVE such as CVE-2019-7070
The CVSS v3.0 score for this CloseEvent. Example: 8.8
Is the CVE marked as a Known Exploited Vulnerability (KEV)
Is this CVE in open source software with OSS data available?
Is there a Proof of Concept (POC) available for this CVE?
Is this CVE remotely exploitable?
Is there a Nuclei Template available for this CVE?
The URL for the patch for this CVE.
Example: https://helpx.adobe.com/security/products/acrobat/apsb19-07.html
The published date and time for this CVE. Example: 2019-05-24T19:29:02.080
The URL reference for this CVE.
Example: https://www.zerodayinitiative.com/advisories/ZDI-19-210/
The CVSS 3.0 severity for this CVE. Example: severity
The last date and time that this CVE was updated. Example: 2019-08-21T16:20:31.353
The URL for the vendor advisory for this CVE.
Example: vendor_advisory
The vulnerability status this CVE. Example: confirmed
The CPE string for this CVE. Example: cpe:2.3:a:adobe:acrobat_reader_dc:*:*:*:*:continuous:*:*:*
CPE Data
Common Platform Enumeration (CPE) Data
CVSS Data
Common Vulnerability Scoring System (CVSS) Data
EPSS Data
Use After FreeExploit Prediction Scoring System (EPSS) Data
HackerOne Data
KVE Data
Known Exploited Vulnerability (KEV) Data
Nuclei Template Data
Open Source Software (OSS) Data
Proof of Concept (POC) Data
Shodan Data
CWE Data
Common Weakness Enumeration (CWE) Data