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 .
Crate jinshu-utils
Dependencies (6 total, 2 outdated, 1 possibly insecure)
Dev dependencies (3 total, 1 outdated, 1 possibly insecure)
Crate Required Latest Status tokio ⚠️ ^1.17
1.47.1
maybe insecure rand ^0.8
0.9.2
out of date serde_json ^1
1.0.142
up to date
Crate jinshu-protocol
Dependencies (13 total, 2 outdated)
Crate jinshu-sdk
Dependencies (14 total, 5 outdated, 1 possibly insecure)
Dev dependencies (1 total, all up-to-date)
Crate Required Latest Status tracing ^0.1
0.1.41
up to date
Crate jinshu-database
Dependencies (3 total, 2 outdated)
Crate Required Latest Status sea-orm ^0.7
1.1.14
out of date serde ^1
1.0.219
up to date time ^0.2.27
0.3.41
out of date
Crate jinshu-redis
Dependencies (5 total, 3 outdated)
Crate jinshu-queue
Dependencies (10 total, 3 outdated, 1 possibly insecure)
Crate jinshu-tracing
Dependencies (7 total, 3 outdated)
Crate jinshu-common
Dependencies (4 total, 3 outdated)
Crate Required Latest Status clap ^3
4.5.42
out of date serde ^1
1.0.219
up to date config ^0.12
0.15.13
out of date thiserror ^1
2.0.12
out of date
Dev dependencies (3 total, all up-to-date)
Crate Required Latest Status temp-dir ^0.1
0.1.16
up to date serde_json ^1
1.0.142
up to date uuid ^1.0.0-alpha.1
1.17.0
up to date
Crate jinshu-rpc
Dependencies (15 total, 7 outdated, 1 possibly insecure)
Dev dependencies (4 total, 1 outdated, 1 possibly insecure)
Crate Required Latest Status rand ^0.8
0.9.2
out of date uuid ^1.0.0-alpha.1
1.17.0
up to date tokio ⚠️ ^1.17
1.47.1
maybe insecure tokio-stream ^0.1
0.1.17
up to date
Build dependencies (2 total, 1 outdated)
Crate jinshu-api
No external dependencies! 🙌
Crate jinshu-comet
Dependencies (17 total, 4 outdated, 1 possibly insecure)
Crate jinshu-receiver
Dependencies (10 total, 4 outdated, 1 possibly insecure)
Crate Required Latest Status tokio ⚠️ ^1.17
1.47.1
maybe insecure futures ^0.3
0.3.31
up to date tonic ^0.6
0.14.0
out of date anyhow ^1
1.0.98
up to date url ^2.2
2.5.4
up to date config ^0.12
0.15.13
out of date tracing ^0.1
0.1.41
up to date serde ^1
1.0.219
up to date rdkafka ^0.28
0.38.0
out of date pulsar ^4.1
6.3.1
out of date
Crate jinshu-gateway
Dependencies (10 total, 4 outdated, 1 possibly insecure)
Dev dependencies (4 total, 2 outdated)
Crate Required Latest Status reqwest ^0.11
0.12.22
out of date argon2 ^0.4
0.5.3
out of date url ^2
2.5.4
up to date serde_repr ^0.1
0.1.20
up to date
Crate jinshu-pusher
Dependencies (10 total, 3 outdated, 1 possibly insecure)
Crate jinshu-timer
No external dependencies! 🙌
Crate jinshu-admin
No external dependencies! 🙌
Crate jinshu-storage
Dependencies (7 total, 1 outdated, 1 possibly insecure)
Crate jinshu-authorizer
Dependencies (8 total, 2 outdated, 1 possibly insecure)
Crate jinshu-file
No external dependencies! 🙌
Security Vulnerabilities tokio
: reject_remote_clients Configuration corruptionRUSTSEC-2023-0001
On 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
.
Workarounds
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);
Patched
>=1.18.4, <1.19.0
>=1.20.3, <1.21.0
>=1.23.1