Vulnerability in trust-dns and trust-dns-server #1703
Merged
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.
An attacker can form packet loops between vulnerable instances, leading to a denial-of-service for both network and CPU resources.
My supervisor (@crossow) and I found and reported the issue. @bluejekyll and @djc have acknowledged and resolved the issue.
Questions:
trust-dns
andtrust-dns-server
. Is there a way to have a single advisory (i.e., single identifier) target multiple crates?trust_dns_server::server::ServerFuture
, not a specific public function. It seems that cannot be encoded via[affected]
.