Temporarily ignore RUSTSEC-2025-0009 for internal substrate deps#1479
Merged
dmitrylavrenov merged 3 commits intomasterfrom Mar 7, 2025
Merged
Temporarily ignore RUSTSEC-2025-0009 for internal substrate deps#1479dmitrylavrenov merged 3 commits intomasterfrom
dmitrylavrenov merged 3 commits intomasterfrom
Conversation
MOZGIII
approved these changes
Mar 7, 2025
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
https://rustsec.org/advisories/RUSTSEC-2025-0009.html
v0.17.7to fixedv0.17.13v0.16.20that is a part ofsubstratedeps part ofrustls 0.20.9part of libp2p internal deps mostly. Of course, we would bump it as soon we bump substrateBtw, the vulnerability description looks like that it shouldn't affect our code as
Protocols like TLS and SSH are not affected by this because those protocols break large amounts of data into small chunks.