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 reqwest

Dependencies

(40 total, 7 outdated, 3 possibly insecure)

CrateRequiredLatestStatus
 bytes^1.01.1.0up to date
 http^0.20.2.5up to date
 mime_guess^2.02.0.3up to date
 serde^1.01.0.130up to date
 serde_json^1.01.0.68up to date
 serde_urlencoded^0.70.7.0up to date
 url^2.22.2.2up to date
 async-compression^0.3.70.3.8up to date
 base64^0.130.13.0up to date
 cookie^0.140.15.1out of date
 cookie_store^0.120.15.0out of date
 encoding_rs^0.80.8.29up to date
 futures-core^0.3.00.3.17up to date
 futures-util^0.3.00.3.17up to date
 http-body^0.4.00.4.3up to date
 hyper ⚠️^0.140.14.13maybe insecure
 hyper-rustls^0.22.10.22.1up to date
 hyper-tls^0.50.5.0up to date
 ipnet^2.32.3.1up to date
 lazy_static^1.41.4.0up to date
 log^0.40.4.14up to date
 mime^0.3.160.3.16up to date
 native-tls^0.2.80.2.8up to date
 percent-encoding^2.12.1.0up to date
 pin-project-lite^0.2.00.2.7up to date
 rustls^0.190.20.0out of date
 rustls-native-certs^0.50.5.0up to date
 time ⚠️^0.2.110.3.3out of date
 tokio ⚠️^1.01.12.0maybe insecure
 tokio-native-tls^0.3.00.3.0up to date
 tokio-rustls^0.220.23.0out of date
 tokio-socks^0.5.10.5.1up to date
 tokio-util^0.6.00.6.8up to date
 trust-dns-resolver^0.200.20.3up to date
 webpki-roots^0.210.22.1out of date
 js-sys^0.3.450.3.55up to date
 wasm-bindgen^0.2.680.2.78up to date
 wasm-bindgen-futures^0.4.180.4.28up to date
 web-sys^0.3.250.3.55up to date
 winreg^0.70.10.1out of date

Dev dependencies

(9 total, 1 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 brotli^3.3.03.3.2up to date
 doc-comment^0.30.3.3up to date
 env_logger^0.80.9.0out of date
 hyper ⚠️^0.140.14.13maybe insecure
 libflate^1.01.1.1up to date
 serde^1.01.0.130up to date
 tokio ⚠️^1.01.12.0maybe insecure
 wasm-bindgen^0.2.680.2.78up to date
 wasm-bindgen-test^0.30.3.28up to date

Security Vulnerabilities

time: Potential segfault in the time crate

RUSTSEC-2020-0071

Impact

Unix-like operating systems may segfault due to dereferencing a dangling pointer in specific circumstances. This requires the user to set any environment variable in a different thread than the affected functions.

The affected functions are:

  • time::UtcOffset::local_offset_at
  • time::UtcOffset::try_local_offset_at
  • time::UtcOffset::current_local_offset
  • time::UtcOffset::try_current_local_offset
  • time::OffsetDateTime::now_local
  • time::OffsetDateTime::try_now_local

Non-Unix targets are unaffected. This includes Windows and wasm.

Patches

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 a the updated, unaffected code.

Workarounds

No workarounds are known.

References

#293

tokio: Task dropped in wrong thread when aborting `LocalSet` task

RUSTSEC-2021-0072

When aborting a task with JoinHandle::abort, the future is dropped in the thread calling abort if the task is not currently being executed. This is incorrect for tasks spawned on a LocalSet.

This can easily result in race conditions as many projects use Rc or RefCell in their Tokio tasks for better performance.

See tokio#3929 for more details.

hyper: Lenient `hyper` header parsing of `Content-Length` could allow request smuggling

RUSTSEC-2021-0078

hyper's HTTP header parser accepted, according to RFC 7230, illegal contents inside Content-Length headers. Due to this, upstream HTTP proxies that ignore the header may still forward them along if it chooses to ignore the error.

To be vulnerable, hyper must be used as an HTTP/1 server and using an HTTP proxy upstream that ignores the header's contents but still forwards it. Due to all the factors that must line up, an attack exploiting this vulnerability is unlikely.

hyper: Integer overflow in `hyper`'s parsing of the `Transfer-Encoding` header leads to data loss

RUSTSEC-2021-0079

When decoding chunk sizes that are too large, hyper's code would encounter an integer overflow. Depending on the situation, this could lead to data loss from an incorrect total size, or in rarer cases, a request smuggling attack.

To be vulnerable, you must be using hyper for any HTTP/1 purpose, including as a client or server, and consumers must send requests or responses that specify a chunk size greater than 18 exabytes. For a possible request smuggling attack to be possible, any upstream proxies must accept a chunk size greater than 64 bits.