-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problem: cargo audit
fails
#20
Comments
Created a PR to upgrade dependencies of |
what about using https://crates.io/crates/bip32 instead of tiny-hderive? |
Created a PR for this: #22. |
Regression in |
Potential segfault in |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Vulnerabilities
RUSTSEC-2021-0076libsecp256k1
0.3.5
paritytech/libsecp256k1#672021-07-13>=0.5.0
libsecp256k1 accepts signatures whose R or S parameter is larger than thesecp256k1 curve order, which differs from other implementations. This could
lead to invalid signatures being verified.
The error is resolved in 0.5.0 by adding a check_overflow flag.RUSTSEC-2021-0073prost-types
0.7.0~
tokio-rs/prost#4382021-07-08>=0.8.0
Affected versions of this crate contained a bug in which untrusted input could cause an overflow and panic when converting aTimestamp
toSystemTime
.It is recommended to upgrade toprost-types
v0.8 and switch the usage ofFrom<Timestamp> for SystemTime
toTryFrom<Timestamp> for SystemTime
.See #438 for more information.RUSTSEC-2020-0159
chrono
0.4.19
Unix-like operating systems may segfault due to dereferencing a dangling pointer in specific circumstances. This requires an environment variable to be set in a different thread than the affected functions. This may occur without the user's knowledge, notably in a third-party library.
No workarounds are known.
The text was updated successfully, but these errors were encountered: