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-http(44 total, 24 outdated, 8 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| actix-codec ⚠️ | ^0.1.2 | 0.5.2 | out of date |
| actix-connect | ^0.2.4 | 2.0.0 | out of date |
| actix-server-config | ^0.1.2 | 0.2.0 | out of date |
| actix-service | ^0.4.1 | 2.0.2 | out of date |
| actix-threadpool | ^0.1.1 | 0.3.3 | out of date |
| actix-utils | ^0.4.4 | 3.0.1 | out of date |
| base64 | ^0.10 | 0.22.1 | out of date |
| bitflags | ^1.0 | 2.6.0 | out of date |
| brotli2 | ^0.3.2 | 0.3.2 | up to date |
| bytes | ^0.4 | 1.8.0 | out of date |
| chrono ⚠️ | ^0.4.6 | 0.4.38 | maybe insecure |
| copyless | ^0.1.4 | 0.1.5 | up to date |
| derive_more | ^0.15.0 | 1.0.0 | out of date |
| either | ^1.5.2 | 1.13.0 | up to date |
| encoding_rs | ^0.8 | 0.8.35 | up to date |
| failure | ^0.1.5 | 0.1.8 | up to date |
| flate2 | ^1.0.7 | 1.0.34 | up to date |
| futures | ^0.1.25 | 0.3.31 | out of date |
| h2 ⚠️ | ^0.1.16 | 0.4.6 | out of date |
| hashbrown | ^0.6.3 | 0.15.1 | out of date |
| http ⚠️ | ^0.1.17 | 1.1.0 | out of date |
| httparse | ^1.3 | 1.9.5 | up to date |
| indexmap | ^1.2 | 2.6.0 | out of date |
| language-tags | ^0.2 | 0.3.2 | out of date |
| lazy_static | ^1.0 | 1.5.0 | up to date |
| log | ^0.4 | 0.4.22 | up to date |
| mime | ^0.3 | 0.3.17 | up to date |
| openssl ⚠️ | ^0.10 | 0.10.68 | maybe insecure |
| percent-encoding | ^2.1 | 2.3.1 | up to date |
| rand | ^0.7 | 0.8.5 | out of date |
| regex ⚠️ | ^1.0 | 1.11.1 | maybe insecure |
| ring | ^0.14.6 | 0.17.8 | out of date |
| rustls ⚠️ | ^0.15.2 | 0.23.16 | out of date |
| serde | ^1.0 | 1.0.214 | up to date |
| serde_json | ^1.0 | 1.0.132 | up to date |
| serde_urlencoded | ^0.6.1 | 0.7.1 | out of date |
| sha1 | ^0.6 | 0.10.6 | out of date |
| slab | ^0.4 | 0.4.9 | up to date |
| time ⚠️ | ^0.1.42 | 0.3.36 | out of date |
| tokio-current-thread | ^0.1 | 0.1.7 | up to date |
| tokio-tcp | ^0.1.3 | 0.1.4 | up to date |
| tokio-timer | ^0.2.8 | 0.2.13 | up to date |
| trust-dns-resolver | ^0.11.1 | 0.23.2 | out of date |
| webpki-roots | ^0.16 | 0.26.6 | out of date |
(8 total, 5 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| actix-connect | ^0.2.0 | 2.0.0 | out of date |
| actix-http-test | ^0.2.4 | 3.2.0 | out of date |
| actix-rt | ^0.2.2 | 2.10.0 | out of date |
| actix-server | ^0.6.0 | 2.5.0 | out of date |
| env_logger | ^0.6 | 0.11.5 | out of date |
| openssl ⚠️ | ^0.10 | 0.10.68 | maybe insecure |
| serde_derive | ^1.0 | 1.0.214 | up to date |
| tokio-tcp | ^0.1 | 0.1.4 | up to date |
http: Integer Overflow in HeaderMap::reserve() can cause Denial of ServiceHeaderMap::reserve() used usize::next_power_of_two() to calculate the increased capacity.
However, next_power_of_two() silently overflows to 0 if given a sufficiently large number
in release mode.
If the map was not empty when the overflow happens,
the library will invoke self.grow(0) and start infinite probing.
This allows an attacker who controls the argument to reserve()
to cause a potential denial of service (DoS).
The flaw was corrected in 0.1.20 release of http crate.
http: HeaderMap::Drain API is unsoundAffected versions of this crate incorrectly used raw pointer, which introduced unsoundness in its public safe API.
Failing to drop the Drain struct causes double-free, and it is possible to violate Rust's alias rule and cause data race with Drain's Iterator implementation.
The flaw was corrected in 0.1.20 release of http crate.
actix-codec: Use-after-free in Framed due to lack of pinningAffected versions of this crate did not require the buffer wrapped in Framed 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 affected functions 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:
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.
regex: Regexes with large repetitions on empty sub-expressions take a very long time to parseThe Rust Security Response WG was notified that the regex crate did not
properly limit the complexity of the regular expressions (regex) it parses. An
attacker could use this security issue to perform a denial of service, by
sending a specially crafted regex to a service accepting untrusted regexes. No
known vulnerability is present when parsing untrusted input with trusted
regexes.
This issue has been assigned CVE-2022-24713. The severity of this vulnerability
is "high" when the regex crate is used to parse untrusted regexes. Other uses
of the regex crate are not affected by this vulnerability.
The regex crate features built-in mitigations to prevent denial of service
attacks caused by untrusted regexes, or untrusted input matched by trusted
regexes. Those (tunable) mitigations already provide sane defaults to prevent
attacks. This guarantee is documented and it's considered part of the crate's
API.
Unfortunately a bug was discovered in the mitigations designed to prevent untrusted regexes to take an arbitrary amount of time during parsing, and it's possible to craft regexes that bypass such mitigations. This makes it possible to perform denial of service attacks by sending specially crafted regexes to services accepting user-controlled, untrusted regexes.
All versions of the regex crate before or equal to 1.5.4 are affected by this
issue. The fix is include starting from regex 1.5.5.
We recommend everyone accepting user-controlled regexes to upgrade immediately
to the latest version of the regex crate.
Unfortunately there is no fixed set of problematic regexes, as there are practically infinite regexes that could be crafted to exploit this vulnerability. Because of this, we do not recommend denying known problematic regexes.
We want to thank Addison Crump for responsibly disclosing this to us according to the Rust security policy, and for helping review the fix.
We also want to thank Andrew Gallant for developing the fix, and Pietro Albini for coordinating the disclosure and writing this advisory.
h2: Resource exhaustion vulnerability in h2 may lead to Denial of Service (DoS)If an attacker is able to flood the network with pairs of HEADERS/RST_STREAM frames, such that the h2 application is not able to accept them faster than the bytes are received, the pending accept queue can grow in memory usage. Being able to do this consistently can result in excessive memory use, and eventually trigger Out Of Memory.
This flaw is corrected in hyperium/h2#668, which restricts remote reset stream count by default.
h2: Resource exhaustion vulnerability in h2 may lead to Denial of Service (DoS)An attacker with an HTTP/2 connection to an affected endpoint can send a steady stream of invalid frames to force the generation of reset frames on the victim endpoint. By closing their recv window, the attacker could then force these resets to be queued in an unbounded fashion, resulting in Out Of Memory (OOM) and high CPU usage.
This fix is corrected in hyperium/h2#737, which limits the total number of internal error resets emitted by default before the connection is closed.
h2: Degradation of service in h2 servers with CONTINUATION FloodAn attacker can send a flood of CONTINUATION frames, causing h2 to process them indefinitely.
This results in an increase in CPU usage.
Tokio task budget helps prevent this from a complete denial-of-service, as the server can still respond to legitimate requests, albeit with increased latency.
More details at "https://seanmonstar.com/blog/hyper-http2-continuation-flood/.
Patches available for 0.4.x and 0.3.x versions.
rustls: `rustls::ConnectionCommon::complete_io` could fall into an infinite loop based on network inputIf a close_notify alert is received during a handshake, complete_io
does not terminate.
Callers which do not call complete_io are not affected.
rustls-tokio and rustls-ffi do not call complete_io
and are not affected.
rustls::Stream and rustls::StreamOwned types use
complete_io and are affected.
openssl: `MemBio::get_buf` has undefined behavior with empty buffersPreviously, MemBio::get_buf called slice::from_raw_parts with a null-pointer, which violates the functions invariants, leading to undefined behavior. In debug builds this would produce an assertion failure. This is now fixed.