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.
rustimate(29 total, 12 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| actix-http ⚠️ | ^1.0.1 | 3.9.0 | out of date |
| actix-rt | ^1.0.0 | 2.10.0 | out of date |
| actix-server | ^1.0.1 | 2.5.0 | out of date |
| actix-service | ^1.0.1 | 2.0.2 | out of date |
| actix-session | ^0.3.0 | 0.10.0 | out of date |
| actix-utils | ^1.0.4 | 3.0.1 | out of date |
| actix-web | ^2.0.0 | 4.9.0 | out of date |
| actix-web-codegen | ^0.2.0 | 4.3.0 | out of date |
| anyhow | ^1.0.26 | 1.0.87 | up to date |
| app_dirs2 | ^2.0.4 | 2.5.5 | up to date |
| arrayvec | ^0.5.1 | 0.7.6 | out of date |
| bincode | ^1.2.1 | 1.3.3 | up to date |
| bitflags | ^1.2.1 | 2.6.0 | out of date |
| clap | ^2.33.0 | 4.5.17 | out of date |
| failure | ^0.1.6 | 0.1.8 | up to date |
| flate2 | ^1.0.13 | 1.0.33 | up to date |
| futures | ^0.3.1 | 0.3.30 | up to date |
| http | ^0.2.0 | 1.1.0 | out of date |
| iovec | ^0.1.4 | 0.1.4 | up to date |
| libc | ^0.2.66 | 0.2.158 | up to date |
| nodrop | ^0.1.14 | 0.1.14 | up to date |
| ryu | ^1.0.2 | 1.0.18 | up to date |
| serde_json | ^1.0.44 | 1.0.128 | up to date |
| slog | ^2.5.2 | 2.7.0 | up to date |
| slog-async | ^2.3.0 | 2.8.0 | up to date |
| slog-json | ^2.3.0 | 2.6.1 | up to date |
| slog-term | ^2.4.2 | 2.9.1 | up to date |
| tokio-reactor | ^0.1.11 | 0.1.12 | up to date |
| tokio-sync | ^0.1.7 | 0.1.8 | up to date |
(1 total, all up-to-date)
| Crate | Required | Latest | Status |
|---|---|---|---|
| winres | ^0.1 | 0.1.12 | up to date |
rustimate-controllers(18 total, 10 outdated, 2 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| actix | ^0.9.0 | 0.13.5 | out of date |
| actix-http ⚠️ | ^1.0.1 | 3.9.0 | out of date |
| actix-service | ^1.0.1 | 2.0.2 | out of date |
| actix-session | ^0.3.0 | 0.10.0 | out of date |
| actix-web | ^2.0.0 | 4.9.0 | out of date |
| actix-web-actors | ^2.0.0 | 4.3.1+deprecated | out of date |
| anyhow | ^1.0.26 | 1.0.87 | up to date |
| bytes | ^0.5.3 | 1.7.1 | out of date |
| chrono ⚠️ | ^0.4.10 | 0.4.38 | maybe insecure |
| derive_more | ^0.99.2 | 1.0.0 | out of date |
| futures | ^0.3.1 | 0.3.30 | up to date |
| maud | ^0.21.0 | 0.26.0 | out of date |
| mime | ^0.3.14 | 0.3.17 | up to date |
| mime_guess | ^2.0.1 | 2.0.5 | up to date |
| serde | ^1.0.104 | 1.0.210 | up to date |
| serde_json | ^1.0.44 | 1.0.128 | up to date |
| slog | ^2.5.2 | 2.7.0 | up to date |
| uuid | ^0.8.1 | 1.10.0 | out of date |
rustimate-core(6 total, 2 outdated)
| Crate | Required | Latest | Status |
|---|---|---|---|
| anyhow | ^1.0.26 | 1.0.87 | up to date |
| bincode | ^1.2.1 | 1.3.3 | up to date |
| derive_more | ^0.99.2 | 1.0.0 | out of date |
| serde | ^1.0.104 | 1.0.210 | up to date |
| serde_json | ^1.0.44 | 1.0.128 | up to date |
| uuid | ^0.8.1 | 1.10.0 | out of date |
(1 total, 1 outdated)
| Crate | Required | Latest | Status |
|---|---|---|---|
| built | ^0.3.2 | 0.7.4 | out of date |
rustimate-service(6 total, 1 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| anyhow | ^1.0.26 | 1.0.87 | up to date |
| chrono ⚠️ | ^0.4.9 | 0.4.38 | maybe insecure |
| serde | ^1.0.104 | 1.0.210 | up to date |
| serde_json | ^1.0.44 | 1.0.128 | up to date |
| slog | ^2.5.2 | 2.7.0 | up to date |
| uuid | ^0.8.1 | 1.10.0 | out of date |
rustimate-templates(5 total, 2 outdated)
| Crate | Required | Latest | Status |
|---|---|---|---|
| anyhow | ^1.0.26 | 1.0.87 | up to date |
| maud | ^0.21.0 | 0.26.0 | out of date |
| num_cpus | ^1.11.1 | 1.16.0 | up to date |
| serde | ^1.0.104 | 1.0.210 | up to date |
| uuid | ^0.8.1 | 1.10.0 | out of date |
rustimate-assets(1 total, 1 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| rust-embed ⚠️ | ^5.2.0 | 8.5.0 | out of date |
rustimate-client(9 total, 2 outdated)
| Crate | Required | Latest | Status |
|---|---|---|---|
| anyhow | ^1.0.26 | 1.0.87 | up to date |
| console_error_panic_hook | ^0.1.6 | 0.1.7 | up to date |
| instant | ^0.1.2 | 0.1.13 | up to date |
| js-sys | ^0.3.33 | 0.3.70 | up to date |
| maud | ^0.21.0 | 0.26.0 | out of date |
| uuid | ^0.8.1 | 1.10.0 | out of date |
| wasm-bindgen | ^0.2.56 | 0.2.93 | up to date |
| wasm-bindgen-futures | ^0.4.6 | 0.4.43 | up to date |
| web-sys | ^0.3.33 | 0.3.70 | up to date |
(1 total, all up-to-date)
| Crate | Required | Latest | Status |
|---|---|---|---|
| wasm-bindgen-test | ^0.3.6 | 0.3.43 | up to date |
actix-http: Use-after-free in BodyStream due to lack of pinningAffected versions of this crate did not require the buffer wrapped in BodyStream to be pinned,
but treated it as if it had a fixed location in memory. This may result in a use-after-free.
The flaw was corrected by making the trait MessageBody require Unpin
and making poll_next() function accept Pin<&mut Self> instead of &mut self.
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.
actix-http: Potential request smuggling capabilities due to lack of input validationAffected versions of this crate did not properly detect invalid requests that could allow HTTP/1 request smuggling (HRS) attacks when running alongside a vulnerable front-end proxy server. This can result in leaked internal and/or user data, including credentials, when the front-end proxy is also vulnerable.
Popular front-end proxies and load balancers already mitigate HRS attacks so it is recommended that they are also kept up to date; check your specific set up. You should upgrade even if the front-end proxy receives exclusively HTTP/2 traffic and connects to the back-end using HTTP/1; several downgrade attacks are known that can also expose HRS vulnerabilities.
rust-embed: RustEmbed generated `get` method allows for directory traversal when reading files from diskWhen running in debug mode and the debug-embed (off by default) feature is
not enabled, the generated get method does not check that the input path is
a child of the folder given.
This allows attackers to read arbitrary files in the file system if they have
control over the filename given. The following code will print the contents of
your /etc/passwd if adjusted with a correct number of ../s depending on
where it is run from.
#[derive(rust_embed::RustEmbed)]
#[folder = "src/"]
pub struct Asset;
fn main() {
let d = Asset::get("../../../etc/passwd").unwrap().data;
println!("{}", String::from_utf8_lossy(&d));
}
The flaw was corrected by canonicalizing the input filename and ensuring that it starts with the canonicalized folder path.