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 isahc

Dependencies

(17 total, 7 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 bytes^0.41.6.0out of date
 chrono ⚠️^0.40.4.38maybe insecure
 crossbeam-channel^0.30.5.12out of date
 crossbeam-utils^0.60.8.19out of date
 curl^0.4.250.4.46up to date
 curl-sys^0.4.230.4.72+curl-8.6.0up to date
 futures-io-preview^0.3.0-alpha.180.2.2up to date
 futures-util-preview^0.3.0-alpha.180.2.2up to date
 http ⚠️^0.11.1.0out of date
 lazy_static^11.4.0up to date
 log^0.40.4.21up to date
 parking_lot^0.90.12.1out of date
 publicsuffix^1.52.2.3out of date
 serde^1.01.0.198up to date
 serde_json^1.01.0.116up to date
 slab^0.40.4.9up to date
 sluice^0.4.20.5.5out of date

Dev dependencies

(8 total, 3 outdated)

CrateRequiredLatestStatus
 env_logger^0.70.11.3out of date
 flate2^1.01.0.28up to date
 futures-preview^0.3.0-alpha.180.2.2up to date
 indicatif^0.120.17.8out of date
 mockito^0.211.4.0out of date
 rayon^11.10.0up to date
 speculate^0.10.1.2up to date
 structopt^0.30.3.26up to date

Security Vulnerabilities

http: Integer Overflow in HeaderMap::reserve() can cause Denial of Service

RUSTSEC-2019-0033

HeaderMap::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 unsound

RUSTSEC-2019-0034

chrono: Potential segfault in `localtime_r` invocations

RUSTSEC-2020-0159

Impact

Unix-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.

Workarounds

No workarounds are known.

References