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.
tentacle-ping(6 total, 3 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| bytes | ^0.4 | 1.6.0 | out of date |
| flatbuffers ⚠️ | ^0.5.0 | 24.3.25 | out of date |
| fnv | ^1.0.6 | 1.0.7 | up to date |
| generic-channel | ^0.2.0 | 0.2.0 | up to date |
| log | ^0.4 | 0.4.21 | up to date |
| tentacle | ^0.2.0-alpha.1 | 0.4.2 | out of date |
flatbuffers: Unsound `impl Follow for bool`The implementation of impl Follow for bool allows to reinterpret arbitrary bytes as a bool.
In Rust bool has stringent requirements for its in-memory representation. Use of this function
allows to violate these requirements and invoke undefined behaviour in safe code.
flatbuffers: `read_scalar` and `read_scalar_at` allow transmuting values without `unsafe` blocksThe read_scalar and read_scalar_at functions are unsound
because they allow transmuting values without unsafe blocks.
The following example shows how to create a dangling reference:
fn main() {
#[derive(Copy, Clone, PartialEq, Debug)]
struct S(&'static str);
impl flatbuffers::EndianScalar for S {
fn to_little_endian(self) -> Self { self }
fn from_little_endian(self) -> Self { self }
}
println!("{:?}", flatbuffers::read_scalar::<S>(&[1; std::mem::size_of::<S>()]));
}
flatbuffers: Generated code can read and write out of bounds in safe codeCode generated by flatbuffers' compiler is unsafe but not marked as such.
See https://github.com/google/flatbuffers/issues/6627 for details.
For example, if generated code is used to decode malformed or untrusted input,
undefined behavior (and thus security vulnerabilities) is possible even without
the use of the unsafe keyword, violating the the meaning of "safe" code;
All users that use generated code by flatbuffers compiler are recommended to:
follow, push, or any method that uses them
(e.g. self_follow).