Updated dependency versions with outstanding CSVs #939
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
…ag fixes this issue
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.
This repo was recently moved from Granulate to Intel in GitHub. In the processes, IPASS scans were enabled and several CVEs in dependency versions were identified. This PR upgrades the packages with the versions that mitigate these CVEs.
Description
The changes involve in bumping the versions of dependent modules to version where CVEs are resolved. Which are as follows:
CVE CVSS Severity Package Version Fixed Version SLA Date
CVE-2023-49797 8.8 High. pyinstaller 4.6 5.13.1 2024-03-08
CVE-2024-6345 8.8 High setuptools 65.5.1 70.0.0 2024-10-13
CVE-2024-35195 5.6 Moderate requests 2.31.0 2.32.0 2024-08-19
CVE-2024-21503 5.3 Moderate black 23.3.0 24.3.0 2024-06-18
Related Issue
Motivation and Context
This change is required by the Intel open source repo maintainers. The general policy is to have all outstanding CVEs mitigated or dispositioned (through an exception) with 90 days of its detection. Failure to do so causes repos to be archived.
How Has This Been Tested?
This is being test with existing unit test
Screenshots
Checklist: