Add vulnerabilities and change packages in some Windows upgrade cases #5234
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.
Description
This PR aims to add some vulnerabilities in the
vuln_packages.json
file that were not contemplated before and add some new packages not vulnerable in some Windows upgrade cases. Thetest_vulnerability.yaml
file has also been modified to incorporate these changes.Testing performed
These changes have been tested locally by running only the cases that have been modified, that is, from the
upgrade_package_maintain_add_vulnerability0
case onwards. The tests have failed, but in the alert file, you can see the alerts corresponding to the vulnerabilities of each installed package, so the test performance is as expected. The errors are due to the tests failing to detect vulnerabilities because of a change in the index reported in #5239.Report: report.zip