mirror of
https://github.com/fleetdm/fleet
synced 2026-05-18 14:38:53 +00:00
| .. | ||
| sync | ||
| cpe.go | ||
| cpe_matching_rule.go | ||
| cpe_matching_rule_test.go | ||
| cpe_matching_rules.go | ||
| cpe_test.go | ||
| cpe_translations.go | ||
| cpe_translations.json | ||
| cve.go | ||
| cve_test.go | ||
| db.go | ||
| indexed_cpe_item.go | ||
| README.md | ||
| sanitize.go | ||
| sanitize_test.go | ||
| sync.go | ||
| sync_test.go | ||
| testing_utils.go | ||
Testing CPE Translations
To improve accuracy when mapping software to CVEs, we can add data to cpe_translations.json which will get picked up by the NVD repo.
To test these changes locally, you can:
-
make the appropriate changes to cpe_translations
-
host this file on a local web server
./tools/file-server 8082 ./server/vulnerabilities/nvd/cpe_translations.json -
(re)launch your local fleet server with the following
--configvulnerabilities: cpe_translations_url: "http://localhost:8082/cpe_translations.json" -
trigger the vulnerabilities scan
fleetctl trigger --name vulnerabilities