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.
libp2p-mplex(10 total, 5 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| asynchronous-codec | ^0.6 | 0.7.0 | out of date |
| bytes | ^1 | 1.6.0 | up to date |
| futures | ^0.3.1 | 0.3.30 | up to date |
| libp2p-core ⚠️ | ^0.30.0 | 0.41.2 | out of date |
| log | ^0.4 | 0.4.21 | up to date |
| nohash-hasher | ^0.2 | 0.2.0 | up to date |
| parking_lot | ^0.11 | 0.12.2 | out of date |
| rand | ^0.7 | 0.8.5 | out of date |
| smallvec | ^1.6.1 | 1.13.2 | up to date |
| unsigned-varint | ^0.7 | 0.8.0 | out of date |
(6 total, 4 outdated)
| Crate | Required | Latest | Status |
|---|---|---|---|
| async-std | ^1.7.0 | 1.12.0 | up to date |
| criterion | ^0.3 | 0.5.1 | out of date |
| env_logger | ^0.9 | 0.11.3 | out of date |
| futures | ^0.3 | 0.3.30 | up to date |
| quickcheck | ^0.9 | 1.0.3 | out of date |
| rand | ^0.7 | 0.8.5 | out of date |
libp2p-core: Failure to verify the public key of a `SignedEnvelope` against the `PeerId` in a `PeerRecord`Affected versions of this crate did not check that the public key the signature was created with matches the peer ID of the peer record. Any combination was considered valid.
This allows an attacker to republish an existing PeerRecord with a different PeerId.