Deps.rs

spectra 0.13.0

[![dependency status](https://deps.rs/crate/spectra/0.13.0/status.svg)](https://deps.rs/crate/spectra/0.13.0)

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 spectra

Dependencies

(17 total, 9 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 alto^3.03.0.4up to date
 any-cache^0.20.2.3up to date
 cgmath^0.160.18.0out of date
 cheddar^0.10.2.1out of date
 chrono ⚠️^0.40.4.38maybe insecure
 clap^2.274.5.4out of date
 image ⚠️^0.190.25.1out of date
 luminance^0.300.47.0out of date
 luminance-glfw^0.50.18.3out of date
 luminance-windowing^0.20.10.1out of date
 num-traits^0.20.2.18up to date
 serde^1.01.0.198up to date
 serde_derive^1.01.0.198up to date
 serde_json^1.01.0.116up to date
 vorbis^0.10.1.0up to date
 warmy^0.70.13.0out of date
 wavefront_obj^5.110.0.0out of date

Dev dependencies

(1 total, 1 outdated)

CrateRequiredLatestStatus
 rand^0.50.8.5out 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