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.
indradb(11 total, 4 outdated, 2 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| async-std | ^1.0 | 1.12.0 | up to date |
| capnp ⚠️ | ^0.11.0 | 0.19.3 | out of date |
| capnp-rpc | ^0.11.0 | 0.19.0 | out of date |
| chrono ⚠️ | ^0.4.10 | 0.4.38 | maybe insecure |
| failure | ^0.1.6 | 0.1.8 | up to date |
| futures | ^0.3.0 | 0.3.30 | up to date |
| indradb-lib | ^1.0.2 | 4.0.0 | out of date |
| lazy_static | ^1.4.0 | 1.4.0 | up to date |
| num_cpus | ^1.11.1 | 1.16.0 | up to date |
| serde_json | ^1.0.44 | 1.0.116 | up to date |
| uuid | ^0.8.1 | 1.8.0 | out of date |
chrono: Potential segfault in `localtime_r` invocationsUnix-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.
No workarounds are known.
capnp: out-of-bounds read possible when setting list-of-pointersIf a message consumer expects data of type "list of pointers", and if the consumer performs certain specific actions on such data, then a message producer can cause the consumer to read out-of-bounds memory. This could trigger a process crash in the consumer, or in some cases could allow exfiltration of private in-memory data.
The C++ Cap'n Proto library is also affected by this bug. See the advisory on the main Cap'n Proto repo for a succinct description of the exact circumstances in which the problem can arise.