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 e2r

Dependencies

(11 total, 8 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 chrono ⚠️^0.4.00.4.37maybe insecure
 gl^0.6.30.14.0out of date
 glutin^0.12.00.31.3out of date
 image ⚠️^0.17.00.25.0out of date
 libc^0.2.260.2.153up to date
 log^0.4.10.4.21up to date
 mazth^0.2.10.6.0out of date
 num^0.1.400.4.1out of date
 pretty_env_logger^0.2.00.5.0out of date
 rand^0.30.8.5out of date
 zpatial^0.0.00.4.3out of date

Security Vulnerabilities

image: Flaw in interface may drop uninitialized instance of arbitrary types

RUSTSEC-2019-0014

Affected versions of this crate would call Vec::set_len on an uninitialized vector with user-provided type parameter, in an interface of the HDR image format decoder. They would then also call other code that could panic before initializing all instances.

This could run Drop implementations on uninitialized types, equivalent to use-after-free, and allow an attacker arbitrary code execution.

Two different fixes were applied. It is possible to conserve the interface by ensuring proper initialization before calling Vec::set_len. Drop is no longer called in case of panic, though.

Starting from version 0.22, a breaking change to the interface requires callers to pre-allocate the output buffer and pass a mutable slice instead, avoiding all unsafe code.

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