This project might be open to known security vulnerabilities, which can be prevented by tightening the version range of affected dependencies. Find detailed information at the bottom.
caelum-vcdm(12 total, 5 outdated, 2 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| base64 | ^0.10 | 0.22.0 | out of date |
| bytes | ^0.4 | 1.6.0 | out of date |
| chrono ⚠️ | ^0.4.9 | 0.4.38 | maybe insecure |
| ed25519-dalek ⚠️ | ^1.0.0-pre.2 | 2.1.1 | out of date |
| hex | ^0.4 | 0.4.3 | up to date |
| linked-hash-map | ^0.5 | 0.5.6 | up to date |
| rand_core | ^0.5.1 | 0.6.4 | out of date |
| serde | ^1.0 | 1.0.198 | up to date |
| serde_json | ^1.0 | 1.0.116 | up to date |
| sha2 | ^0.8 | 0.10.8 | out of date |
| stdweb | ^0.4.20 | 0.4.20 | up to date |
| wasm-bindgen | ^0.2 | 0.2.92 | up to date |
(2 total, 2 outdated)
| Crate | Required | Latest | Status |
|---|---|---|---|
| rand_core | ^0.5.1 | 0.6.4 | out of date |
| wasm-bindgen-test | ^0.2 | 0.3.42 | out of date |
chrono: Potential segfault in `localtime_r` invocationsUnix-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.
ed25519-dalek: Double Public Key Signing Function Oracle Attack on `ed25519-dalek`Versions of ed25519-dalek prior to v2.0 model private and public keys as
separate types which can be assembled into a Keypair, and also provide APIs
for serializing and deserializing 64-byte private/public keypairs.
Such APIs and serializations are inherently unsafe as the public key is one of
the inputs used in the deterministic computation of the S part of the signature,
but not in the R value. An adversary could somehow use the signing function as
an oracle that allows arbitrary public keys as input can obtain two signatures
for the same message sharing the same R and only differ on the S part.
Unfortunately, when this happens, one can easily extract the private key.
Revised public APIs in v2.0 of ed25519-dalek do NOT allow a decoupled
private/public keypair as signing input, except as part of specially labeled
"hazmat" APIs which are clearly labeled as being dangerous if misused.