Bump certifi from 2023.5.7 to 2023.7.22 in /examples #5941
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
There is a securiy vulnerability for certifi versions <2023.7.22 (see details here: https://nvd.nist.gov/vuln/detail/CVE-2023-37920). Even though this version is only in /examples, it gets detected and flagged by static analysis tools when scanning docker images that have the latest version of pipenv installed.
yurishevtsov
changed the title
oz123
approved these changes
Sep 24, 2023
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.
The issue
There is a security vulnerability for
certifiversions <2023.7.22 (see details here: CVE-2023-37920). Even though this version is only in /examples, it gets detected and flagged by static analysis tools when scanning docker images that have the latest version of pipenv installed.Related issue: #5940
The fix
Update
certifiin/examplesto address the issueThe checklist
news/directory to describe this fix with the extension.bugfix.rst,.feature.rst,.behavior.rst,.doc.rst..vendor.rst. or.trivial.rst(this will appear in the release changelog). Use semantic line breaks and name the file after the issue number or the PR #.