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.
tlfs(14 total, 6 outdated, 2 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| anyhow | ^1.0.51 | 1.0.82 | up to date |
| async-trait | ^0.1.52 | 0.1.80 | up to date |
| bytecheck | ^0.6.7 | 0.7.0 | out of date |
| ed25519-dalek ⚠️ | ^1.0.1 | 2.1.1 | out of date |
| fnv | ^1.0.7 | 1.0.7 | up to date |
| futures | ^0.3.17 | 0.3.30 | up to date |
| libp2p-broadcast | ^0.7.0 | 0.12.0 | out of date |
| libp2p-webrtc | ^0.2.1 | 0.3.0 | out of date |
| log-panics | ^2.0.0 | 2.1.0 | up to date |
| rkyv | ^0.7.26 | 0.7.44 | up to date |
| tracing | ^0.1.29 | 0.1.40 | up to date |
| tracing-log | ^0.1.2 | 0.2.0 | out of date |
| tracing-subscriber | ^0.3.3 | 0.3.18 | up to date |
| libp2p ⚠️ | ^0.42.0 | 0.53.2 | out of date |
(1 total, all up-to-date)
| Crate | Required | Latest | Status |
|---|---|---|---|
| async-std | ^1.10.0 | 1.12.0 | up to date |
tlfs-crdt(14 total, 4 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| anyhow | ^1.0.51 | 1.0.82 | up to date |
| base64 | ^0.13.0 | 0.22.0 | out of date |
| blake3 | ^1.2.0 | 1.5.1 | up to date |
| bytecheck | ^0.6.7 | 0.7.0 | out of date |
| crepe | ^0.1.5 | 0.1.8 | up to date |
| ed25519-dalek ⚠️ | ^1.0.1 | 2.1.1 | out of date |
| futures | ^0.3.17 | 0.3.30 | up to date |
| getrandom | ^0.2.3 | 0.2.14 | up to date |
| hex | ^0.4.3 | 0.4.3 | up to date |
| parking_lot | ^0.11.2 | 0.12.2 | out of date |
| rkyv | ^0.7.26 | 0.7.44 | up to date |
| smallvec | ^1.7.0 | 1.13.2 | up to date |
| tracing | ^0.1.29 | 0.1.40 | up to date |
| vec-collections | ^0.4.3 | 0.4.3 | up to date |
(5 total, 1 outdated)
| Crate | Required | Latest | Status |
|---|---|---|---|
| async-std | ^1.10.0 | 1.12.0 | up to date |
| log-panics | ^2.0.0 | 2.1.0 | up to date |
| proptest | ^1.0.0 | 1.4.0 | up to date |
| tracing-log | ^0.1.2 | 0.2.0 | out of date |
| tracing-subscriber | ^0.3.3 | 0.3.18 | up to date |
tlfs-api(4 total, all up-to-date)
| Crate | Required | Latest | Status |
|---|---|---|---|
| anyhow | ^1.0.51 | 1.0.82 | up to date |
| ffi-gen | ^0.1.5 | 0.1.13 | up to date |
| ffi-gen-macro | ^0.1.2 | 0.1.2 | up to date |
| futures | ^0.3.17 | 0.3.30 | up to date |
(1 total, all up-to-date)
| Crate | Required | Latest | Status |
|---|---|---|---|
| ffi-gen | ^0.1.5 | 0.1.13 | up to date |
relay(10 total, 4 outdated, 3 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| acme-lib | ^0.8.2 | 0.9.1 | out of date |
| anyhow | ^1.0.51 | 1.0.82 | up to date |
| clap | ^3.0.0-rc.4 | 4.5.4 | out of date |
| hex | ^0.4.3 | 0.4.3 | up to date |
| libp2p ⚠️ | ^0.41.0 | 0.53.2 | out of date |
| rustls-pemfile | ^0.2.1 | 2.1.2 | out of date |
| tokio ⚠️ | ^1.14.0 | 1.37.0 | maybe insecure |
| tracing | ^0.1.29 | 0.1.40 | up to date |
| tracing-subscriber | ^0.3.3 | 0.3.18 | up to date |
| warp ⚠️ | ^0.3.2 | 0.3.7 | maybe insecure |
tlfsc(5 total, 1 outdated)
| Crate | Required | Latest | Status |
|---|---|---|---|
| anyhow | ^1.0.51 | 1.0.82 | up to date |
| clap | ^3.0.0-rc.4 | 4.5.4 | out of date |
| fnv | ^1.0.7 | 1.0.7 | up to date |
| pest | ^2.1.3 | 2.7.9 | up to date |
| pest_derive | ^2.1.0 | 2.7.9 | up to date |
warp: Improper validation of Windows paths could lead to directory traversal attackPath resolution in warp::filters::fs::dir didn't correctly validate Windows paths
meaning paths like /foo/bar/c:/windows/web/screen/img101.png would be allowed
and respond with the contents of c:/windows/web/screen/img101.png. Thus users
could potentially read files anywhere on the filesystem.
This only impacts Windows. Linux and other unix likes are not impacted by this.
libp2p: libp2p Lack of resource management DoSlibp2p allows a potential attacker to cause victim p2p node to run out of memory
The out of memory failure can cause crashes where libp2p is intended to be used within large scale networks leading to potential Denial of Service (DoS) vector
Users should upgrade or reference the DoS mitigation strategies.
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.
tokio: reject_remote_clients Configuration corruptionOn Windows, configuring a named pipe server with pipe_mode will force ServerOptions::reject_remote_clients as false.
This drops any intended explicit configuration for the reject_remote_clients that may have been set as true previously.
The default setting of reject_remote_clients is normally true meaning the default is also overridden as false.
Ensure that pipe_mode is set first after initializing a ServerOptions. For example:
let mut opts = ServerOptions::new();
opts.pipe_mode(PipeMode::Message);
opts.reject_remote_clients(true);