Resolve Python security alerts #2722
Draft
+7
−7
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
StepanBrychta
changed the title
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 does this change?
Resolves the following security alerts by updating Python packages:
Removal of e-Tugra root certificatealertsWerkzeug debugger vulnerable to remote execution when interacting with attacker controlled domainalertsThis is done by updating the
werkzeugandcertifipackages in several Python services.How to test
I believe that no testing is required for this change. We don't use either of these packages directly, and all packages which require either of these packages are version agnostic (verified using the
pipdeptreecommand).Furthermore, the
werkzeugpackage is only used in unit tests (test_requirements.txt), so updating it does not risk breaking production code.How can we measure success?
All listed Python-related security alerts in this repo are addressed.
Have we considered potential risks?