Deps.rs

plotters 0.2.2

[![dependency status](https://deps.rs/crate/plotters/0.2.2/status.svg)](https://deps.rs/crate/plotters/0.2.2)

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 plotters

Dependencies

(10 total, 5 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 chrono ⚠️^0.4.60.4.38maybe insecure
 font-loader^0.8.00.11.0out of date
 image ⚠️^0.21.10.25.1out of date
 js-sys^0.3.40.3.69up to date
 lazy_static^1.21.4.0up to date
 piston_window^0.96.00.131.0out of date
 rusttype^0.7.60.9.3out of date
 svg^0.5.120.17.0out of date
 wasm-bindgen^0.2.430.2.92up to date
 web-sys^0.3.40.3.69up to date

Dev dependencies

(1 total, 1 outdated)

CrateRequiredLatestStatus
 rand^0.6.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