Upgrade spin crate to patch a vulnerability.
#8320
Merged
+4
−4
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
The vulnerability: ``` $ ./build-support/bin/ci.py --cargo-audit ... error: Vulnerable crates found! ID: RUSTSEC-2019-0013 Crate: spin Version: 0.5.1 Date: 2019-08-27 URL: mvdnes/spin-rs#65 Title: Wrong memory orderings in RwLock potentially violates mutual exclusion Solution: upgrade to: >= 0.5.2 error: 1 vulnerability found! Cargo audit failure ``` Although we don't directly depend on `spin`, we depend on `lazy_static` (amongst others) which does: ``` $ (cd src/rust/engine && ../../../build-support/bin/native/cargo tree -p spin -i) spin v0.5.2 ├── lazy_static v1.3.0 ... ``` So this change was generated with a targeted upgrade: ``` $ ./build-support/bin/native/cargo update --manifest-path src/rust/engine/Cargo.toml -p spin --aggressive ```
gshuflin
approved these changes
Sep 24, 2019
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.
The vulnerability:
Although we don't directly depend on
spin, we depend onlazy_static(amongst others) which does:
So this change was generated with a targeted upgrade: