1 min readBy Stackbyte EngineeringAPIs
What a CVE Triage response contains
The fields CVE Triage returns for a vulnerability, and how each response shows the age of its data.
CVE Triage is our first API, and it is now live. This post describes what a response contains. The full field list is in the CVE Triage docs.
Requests
A lookup takes one CVE ID and costs 1 credit. The batch endpoint takes up to 100 CVE IDs and costs 1 credit for every 10, which suits scheduled jobs that check a full scan report. A third endpoint lists CVEs recently added to CISA's Known Exploited Vulnerabilities catalogue.
Fields
The data section contains the description, CVSS base score and severity, CWE classes and references from NVD; the EPSS probability and percentile from FIRST; and, if the CVE is in CISA's KEV catalogue, the date it was added, the due date, the required action and whether it is known to be used in ransomware campaigns. A priority from P1 to P4, with the reason in words, is worked out from those three sources.
Metadata
The meta section lists every source used, with its licence, the date of its data and whether its last nightly import passed its checks. It also shows the credits charged and remaining. If one of the sources has not updated overnight, the response uses the most recent good copy and the date shows how old it is.
Output format
Responses are flat JSON with the same field names on every call, so they can go straight into a SIEM, a ticketing rule or a script. Field names follow the Elastic Common Schema where one exists, and our additions sit under stackbyte.
To try it, get a free key. The Free plan includes 100 credits a month.
Sources
- NVD, National Vulnerability Database
- FIRST, Exploit Prediction Scoring System
- CISA, Known Exploited Vulnerabilities catalogue
Spotted an error? Tell us and we will correct it. Our editorial standards are on the About page.