Tenable seems to be a good source of first-party reference urls to fix information, as such, it should be implemented in a similar fashion to the NVDFixUrlFinder.
Base branch: master
Feature branch fixfinder-tenable-url
Definition of complete:
- A new feature branch is created from the base branch
- A new class
TenableFixUrlFinder is created (extends FixUrlFinder) and modeled after the NVDFixUrlFinder implementation
- The
FixUrlFinder.run() method is overridden to parse reference urls from specifically Tenable pages and return said urls.
- A PR is created, reviewed by @dylan-mulligan, and merged back into the base branch
Example URL:
3rd-party: https://www.tenable.com/cve/CVE-2023-41670 -> 1st-party: https://patchstack.com/database/vulnerability/use-memcached/wordpress-use-memcached-plugin-1-0-5-cross-site-request-forgery-csrf-vulnerability?_s_id=cve
Tenable seems to be a good source of first-party reference urls to fix information, as such, it should be implemented in a similar fashion to the NVDFixUrlFinder.
Base branch:
masterFeature branch
fixfinder-tenable-urlDefinition of complete:
TenableFixUrlFinderis created (extendsFixUrlFinder) and modeled after theNVDFixUrlFinderimplementationFixUrlFinder.run()method is overridden to parse reference urls from specifically Tenable pages and return said urls.Example URL: