This project contains known security vulnerabilities. Find detailed information at the bottom.
prometheus(10 total, 1 insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| cfg-if | ^1.0 | 1.0.0 | up to date |
| fnv | ^1.0 | 1.0.7 | up to date |
| lazy_static | ^1.4 | 1.4.0 | up to date |
| libc | ^0.2 | 0.2.98 | up to date |
| memchr | ^2.3 | 2.4.0 | up to date |
| parking_lot | ^0.11 | 0.11.1 | up to date |
| protobuf | ^2.0 | 2.24.1 | insecure |
| reqwest | ^0.11 | 0.11.4 | up to date |
| thiserror | ^1.0 | 1.0.26 | up to date |
| procfs | ^0.9 | 0.9.1 | up to date |
(4 total, 1 insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| criterion | ^0.3 | 0.3.4 | up to date |
| getopts | ^0.2 | 0.2.21 | up to date |
| hyper | ^0.14 | 0.14.11 | insecure |
| tokio | ^1.0 | 1.9.0 | up to date |
protobuf: Out of Memory in stream::read_raw_bytes_into()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.
hyper: Multiple Transfer-Encoding headers misinterprets request payloadhyper's HTTP server code had a flaw that incorrectly understands some requests with multiple transfer-encoding headers to have a chunked payload, when it should have been rejected as illegal. This combined with an upstream HTTP proxy that understands the request payload boundary differently can result in "request smuggling" or "desync attacks".