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.
oauth2(14 total, 6 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| base64 | ^0.9 | 0.22.0 | out of date |
| curl | ^0.4.0 | 0.4.46 | up to date |
| failure | ^0.1 | 0.1.8 | up to date |
| failure_derive | ^0.1 | 0.1.8 | up to date |
| futures | ^0.1 | 0.3.30 | out of date |
| http ⚠️ | ^0.1 | 1.1.0 | out of date |
| rand | ^0.6 | 0.8.5 | out of date |
| reqwest | ^0.9 | 0.12.4 | out of date |
| serde | ^1.0 | 1.0.198 | up to date |
| serde_derive | ^1.0 | 1.0.198 | up to date |
| serde_json | ^1.0 | 1.0.116 | up to date |
| sha2 | ^0.7 | 0.10.8 | out of date |
| tokio-io | ^0.1 | 0.1.13 | up to date |
| url | ^2.1 | 2.5.0 | up to date |
(1 total, 1 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| tokio ⚠️ | ^0.1 | 1.37.0 | out of 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.
tokio: Data race when sending and receiving after closing a `oneshot` channelIf a tokio::sync::oneshot channel is closed (via the
oneshot::Receiver::close method), a data race may occur if the
oneshot::Sender::send method is called while the corresponding
oneshot::Receiver is awaited or calling try_recv.
When these methods are called concurrently on a closed channel, the two halves of the channel can concurrently access a shared memory location, resulting in a data race. This has been observed to cause memory corruption.
Note that the race only occurs when both halves of the channel are used
after the Receiver half has called close. Code where close is not used, or where the
Receiver is not awaited and try_recv is not called after calling close,
is not affected.
See tokio#4225 for more details.