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 cloudflare

Dependencies

(16 total, 9 outdated, 3 possibly insecure)

CrateRequiredLatestStatus
 chrono ⚠️^0.40.4.38maybe insecure
 clap^2.334.5.4out of date
 http ⚠️^0.1.181.1.0out of date
 maplit^1.01.0.2up to date
 percent-encoding^1.0.12.3.1out of date
 reqwest^0.90.12.4out of date
 serde^1.01.0.198up to date
 serde_derive^1.01.0.198up to date
 serde_json^1.01.0.116up to date
 serde_qs^0.40.13.0out of date
 serde_with^1.3.13.8.0out of date
 serde_yaml ⚠️^0.80.9.34+deprecatedout of date
 slog^2.42.7.0up to date
 slog-term^2.42.9.1up to date
 sloggers^0.32.2.0out of date
 url^1.72.5.0out of date

Security Vulnerabilities

serde_yaml: Uncontrolled recursion leads to abort in deserialization

RUSTSEC-2018-0005

Affected versions of this crate did not properly check for recursion while deserializing aliases.

This allows an attacker to make a YAML file with an alias referring to itself causing an abort.

The flaw was corrected by checking the recursion depth.

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