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 grpcio

Dependencies

(7 total, 5 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 bytes^0.4.111.6.0out of date
 futures^0.1.150.3.30out of date
 grpcio-sys^0.5.0-alpha0.13.0+1.56.2-patchedout of date
 libc^0.20.2.153up to date
 log^0.40.4.21up to date
 prost ⚠️^0.50.12.4out of date
 protobuf ⚠️^2.03.4.0out of date

Dev dependencies

(9 total, 2 outdated)

CrateRequiredLatestStatus
 rand^0.40.8.5out 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
 slog^2.02.7.0up to date
 slog-async^2.12.8.0up to date
 slog-scope^4.04.4.0up to date
 slog-stdlog^3.04.1.1out of date
 slog-term^2.22.9.1up to date

Security Vulnerabilities

protobuf: Out of Memory in stream::read_raw_bytes_into()

RUSTSEC-2019-0003

Affected versions of this crate called Vec::reserve() on user-supplied input.

This allows an attacker to cause an Out of Memory condition while calling the vulnerable method on untrusted data.

prost: Parsing a specially crafted message can result in a stack overflow

RUSTSEC-2020-0002

Affected versions of this crate contained a bug in which decoding untrusted input could overflow the stack.

On architectures with stack probes (like x86), this can be used for denial of service attacks, while on architectures without stack probes (like ARM) overflowing the stack is unsound and can result in potential memory corruption (or even RCE).

The flaw was quickly corrected by @danburkert and released in version 0.6.1.