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.
swgoh_farming_bot(16 total, 4 outdated, 3 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| api-swgoh-gg | ^0.3 | 0.3.0 | up to date |
| dotenv | ^0.15 | 0.15.0 | up to date |
| env_logger | ^0.9 | 0.11.5 | out of date |
| lazy_static | ^1.4 | 1.5.0 | up to date |
| log | ^0.4 | 0.4.22 | up to date |
| numerals | ^0.1 | 0.1.4 | up to date |
| r2d2 | ^0.8.9 | 0.8.10 | up to date |
| serde_json | ^1.0 | 1.0.133 | up to date |
| time | ^0.3 | 0.3.36 | up to date |
| diesel_migrations | ^1.4 | 2.2.0 | out of date |
| tokio-stream | ^0.1 | 0.1.16 | up to date |
| tokio ⚠️ | ^1.16 | 1.41.1 | maybe insecure |
| serenity | ^0.10 | 0.12.4 | out of date |
| chrono ⚠️ | ^0.4 | 0.4.38 | maybe insecure |
| serde | ^1.0 | 1.0.215 | up to date |
| diesel ⚠️ | ^1.4.6 | 2.2.5 | 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.
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);
diesel: Binary Protocol Misinterpretation caused by Truncating or Overflowing CastsThe following presentation at this year's DEF CON was brought to our attention on the Diesel Gitter Channel:
SQL Injection isn't Dead: Smuggling Queries at the Protocol Level
http://web.archive.org/web/20240812130923/https://media.defcon.org/DEF%20CON%2032/DEF%20CON%2032%20presentations/DEF%20CON%2032%20-%20Paul%20Gerste%20-%20SQL%20Injection%20Isn't%20Dead%20Smuggling%20Queries%20at%20the%20Protocol%20Level.pdf
(Archive link for posterity.) Essentially, encoding a value larger than 4GiB can cause the length prefix in the protocol to overflow, causing the server to interpret the rest of the string as binary protocol commands or other data.
It appears Diesel does perform truncating casts in a way that could be problematic, for example: https://github.com/diesel-rs/diesel/blob/ae82c4a5a133db65612b7436356f549bfecda1c7/diesel/src/pg/connection/stmt/mod.rs#L36
This code has existed essentially since the beginning,
so it is reasonable to assume that all published versions <= 2.2.2 are affected.
The prefered migration to the outlined problem is to update to a Diesel version newer than 2.2.2, which includes fixes for the problem.
As always, you should make sure your application is validating untrustworthy user input. Reject any input over 4 GiB, or any input that could encode to a string longer than 4 GiB. Dynamically built queries are also potentially problematic if it pushes the message size over this 4 GiB bound.
For web application backends, consider adding some middleware that limits the size of request bodies by default.
Diesel now uses #[deny] directives for the following Clippy lints:
to prevent casts that will lead to precision loss or other trunctations. Additionally we performed an audit of the relevant code.
A fix is included in the 2.2.3 release.