fix: update certifi version to address CVE-2023-37920 #6509
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.
Summary
Fix image vulnerability from docker and aws inspector scan
Does this close any open issues?
Closes #6508
Screenshots
Other Information
As it has been discussed on psf/requests repo, update certifi version to address critical CVE #6494, maintainers have decided to not update certifi :
I have overridden poetry certifi version dependency to
2023.07.22
as mentioned in fix subdependency versions, while keeping subdeps separated from direct dependencies. #2546It only concerns the
backend/python/pydevlake/pyproject.toml
file since other pyproject files include it as a dependency.Lock files have been updated with
poetry lock --no-update
to keep the same dependencies versions in :backend/python/pydevlake
backend/python/plugins/azuredevops
backend/python/test/fakeplugin