Repository navigation
Conversation
mongodb 3.6.0 pinned hickory-resolver/hickory-proto 0.25 for its mongodb+srv SRV stub resolver, leaving one vulnerable hickory-proto 0.25.2 copy in the tree even after the workspace moved to 0.26.1. mongodb 3.7.0 updated its hickory dependency to 0.26. The lockfile now resolves a single hickory-proto / hickory-resolver 0.26.1 across the whole workspace — the DNS CVEs (NSEC3 unbounded loop, O(n^2) name-compression) are fully cleared, with no residual. Verified: cargo check --bin temps compiles clean against mongodb 3.7.0.
Contributor
Author
|
Closing as no-op: the mongodb 3.7.0 bump is already on |
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
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.
Summary
mongodb+srvSRV stub resolver, leaving one vulnerable hickory-proto 0.25.2 copy in the tree even after the rest of the workspace moved to hickory 0.26.1.cargo treeresolves a single hickory-proto / hickory-resolver 0.26.1 across the whole workspace.Why
Clears the residual DNS CVEs (NSEC3 unbounded loop, O(n²) name compression) reported by
cargo auditagainst hickory-proto 0.25.Test plan
cargo check --bin tempscompiles cleancargo auditshows hickory-proto 0.25.x no longer present in tree