-
Notifications
You must be signed in to change notification settings - Fork 0
/
assets.cfg
29 lines (28 loc) · 1.24 KB
/
assets.cfg
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
# Define in this file the assets you want to monitor.
#
# Create one section per asset, the name of the section being the name of your asset.
#
# Each asset must have at least a 'query' field. The value of this field is looked up (case-insensitively)
# in the 'summary', 'vulnerable_configuration', and 'vulnerable_configuration_cpe_2_2" fields of the CVE's
# to decide if the CVE affects the asset.
# Each asset may also have a 'version' field. If defined, the CVE must also apply to a version at least
# equals to the version field's value. CVESearchMonitor uses the packaging python module for comparing
# versions.
# Finally, each asset may have a 'description' field for documentation purpose
#
# See also provided examples
#[7-zip]
#description = The 7-zip file archiver
#query = 7-zip
#
#[Flash player]
#description = This example shows that it is possible to strengthen the query by using CPE-like format
# (here "vendor:product_partial_name"). In this case, "flash" is a far too common keyword; So, the query
# is strengthen by specifying "adobe:flash"
#query = adobe:flash
#
#[Java Runtime]
#description = This example shows the use of the version field. Only the CVE's that apply to version 1.8.0
# and above will match.
#query = oracle:jre
#version = 1.8