Search Syntax
Building Search Queries
Search queries are built from search terms, separated by spaces. Search terms are built from a key and a value, joined with a colon.
When used with the Search API the querystring portion must be URL-encoded. For example, cURL users can specify -G --data-urlencode "q=score:>90" as part of their command to correctly encode and append the search query.
The result of a search query are those CVEs that match all terms in the query. In other words, terms are combined using AND.
Supported Terms
| Key | Value |
|---|---|
| Search against a CVE’s current score. If you are an Empirical.Models.Global customer, the current global score will be used. If you are an Empirical.Models.EPSS customer, the current EPSS score will be used. In both situations, scores from the latest version of the model will be used. Syntax for specifying score constraints (all scores are specified on a 0-100 scale and may contain decimals):
If multiple score terms are given for a constraint, the final term is used. For example, |
| Search against a CVE’s publication date. Syntax for specifying publication date constraints (should be in the format
If multiple published_at terms are given for a constraint, the final term is used. For example, |
| Alias for |
| One of the following values:
|
| The name of the software vendor responsible for the affected software. Spaces in vendor names should be replaced with underscores, for example: |
| The name of the affected software product. Spaces in product names should be replaced with underscores, for example: |
|
|
|
|