Fix ring vulerability rustsec 2025 0009 #25
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
toadslop
force-pushed
the
fix-ring-vulerability-RUSTSEC-2025-0009
branch
2 times, most recently
from
a0496e3 to
45b2d49
Compare
added 2 commits
March 7, 2025 10:54
toadslop
force-pushed
the
fix-ring-vulerability-RUSTSEC-2025-0009
branch
from
45b2d49 to
cae9695
Compare
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.
Vulnerability found in the Ring crate: RUSTSEC-2025-0009.
This PR includes the results of running
cargo updateand also manually bumping jswonwebtoken, which depends on Ring, to its latest version.