Deps.rs

rendy-texture 0.3.0

[![dependency status](https://deps.rs/crate/rendy-texture/0.3.0/status.svg)](https://deps.rs/crate/rendy-texture/0.3.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 rendy-texture

Dependencies

(12 total, 8 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 derivative^1.02.2.0out of date
 failure^0.10.1.8up to date
 gfx-hal^0.20.9.0out of date
 image ⚠️^0.21.00.25.1out of date
 log^0.40.4.21up to date
 palette^0.40.7.5out of date
 rendy-factory^0.3.00.5.1out of date
 rendy-memory^0.3.00.5.2out of date
 rendy-resource^0.3.00.5.1out of date
 rendy-util^0.3.00.4.1out of date
 serde^1.01.0.198up to date
 thread_profiler^0.30.3.0up 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.