Improve VT version handling for CVE & OVAL results #1496
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The functions make_result and make_cve_result now add a timestamp as nvt_version for CVE and OVAL results.
timopollmeier
added
the
backport-to-main
|
@Mergifyio backport master |
|
Command
|
timopollmeier
added a commit
that referenced
this pull request
Apr 20, 2021
timopollmeier
added a commit
that referenced
this pull request
Apr 20, 2021
Improve VT version handling for CVE & OVAL results (backport #1496)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What:
The functions make_result and make_cve_result now add a timestamp
as nvt_version for CVE and OVAL results.
Why:
To have the VT version available in results more consistently.
How did you test it:
By running a CVE scan and checking the scan_nvt_version of the results.
Checklist: