Update gevent to 23.9.1 to address critical CVE #6485
Closed
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
gpspake
changed the title
|
Oops. Looks like I need to update the lock file (I'm new to poetry). Working on that 🙂. |
update greenlet to 2.0.2 - Because redash depends on gevent (23.9.1) which depends on greenlet (>=2.0.0), greenlet is required. So, because redash depends on greenlet (1.1.3), version solving failed.
|
Also had to update greenlet to 2.0.2 to satisfy gevent requirement |
|
Closing because workflow requirements appear to be stuck |
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 type of PR is this?
Description
Update gevent to 23.9.1 to address criticial CVE flagged by Trivy
How is this tested?
Related Tickets & Documents
Relevant links:
https://nvd.nist.gov/vuln/detail/CVE-2023-41419
https://avd.aquasec.com/nvd/cve-2023-41419
https://www.gevent.org/changelog.html#id1