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.
actix-web-flash(7 total, 4 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| actix-web | ^1 | 4.9.0 | out of date |
| actix-service | ^0.4 | 2.0.2 | out of date |
| actix-http ⚠️ | ^0.2 | 3.9.0 | out of date |
| serde | ^1.0 | 1.0.216 | up to date |
| serde_derive | ^1.0 | 1.0.216 | up to date |
| serde_json | ^1.0 | 1.0.134 | up to date |
| futures | ^0.1 | 0.3.31 | out of date |
(3 total, 3 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| time ⚠️ | ^0.1 | 0.3.37 | out of date |
| actix-files | ^0.1 | 0.6.6 | out of date |
| actix-http-test | ^0.2 | 3.2.0 | out of 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.
time: Potential segfault in the time crateThe affected functions set environment variables without synchronization. On Unix-like operating systems, this can crash in multithreaded programs. Programs may segfault due to dereferencing a dangling pointer if an environment variable is read in a different thread than the affected functions. This may occur without the user's knowledge, notably in the Rust standard library or third-party libraries.
The affected functions from time 0.2.7 through 0.2.22 are:
time::UtcOffset::local_offset_attime::UtcOffset::try_local_offset_attime::UtcOffset::current_local_offsettime::UtcOffset::try_current_local_offsettime::OffsetDateTime::now_localtime::OffsetDateTime::try_now_localThe affected functions in time 0.1 (all versions) are:
time::at_utctime::attime::nowtime::tzsetNon-Unix targets (including Windows and wasm) are unaffected.
Pending a proper fix, the internal method that determines the local offset has been modified to always return None on the affected operating systems. This has the effect of returning an Err on the try_* methods and UTC on the non-try_* methods.
Users and library authors with time in their dependency tree should perform cargo update, which will pull in the updated, unaffected code.
Users of time 0.1 do not have a patch and should upgrade to an unaffected version: time 0.2.23 or greater or the 0.3 series.
A possible workaround for crates affected through the transitive dependency in chrono, is to avoid using the default oldtime feature dependency of the chrono crate by disabling its default-features and manually specifying the required features instead.
Cargo.toml:
chrono = { version = "0.4", default-features = false, features = ["serde"] }
chrono = { version = "0.4.22", default-features = false, features = ["clock"] }
Commandline:
cargo add chrono --no-default-features -F clock
Sources:
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.