Deps.rs

vizia / vizia

[![dependency status](https://deps.rs/repo/github/vizia/vizia/status.svg)](https://deps.rs/repo/github/vizia/vizia)

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 vizia

Dev dependencies

(3 total, 1 possibly insecure)

CrateRequiredLatestStatus
 chrono ⚠️^0.40.4.41maybe insecure
 log^0.40.4.27up to date
 fern^0.70.7.1up to date

Crate todo

No external dependencies! 🙌

Crate widget_gallery

Dependencies

(3 total, all up-to-date)

CrateRequiredLatestStatus
 fern^0.70.7.1up to date
 log^0.4.190.4.27up to date
 chrono^0.4.340.4.41up to date

Crate gallery

Dependencies

(5 total, 1 possibly insecure)

CrateRequiredLatestStatus
 tokio^1.43.01.45.1up to date
 bytes*1.10.1up to date
 image ⚠️*0.25.6maybe insecure
 serde*1.0.219up to date
 reqwest*0.12.20up to 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