Deps.rs

sardonyx_gltf 0.0.3

[![dependency status](https://deps.rs/crate/sardonyx_gltf/0.0.3/status.svg)](https://deps.rs/crate/sardonyx_gltf/0.0.3)

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 sardonyx_gltf

Dependencies

(17 total, 8 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 base64^0.100.22.1out of date
 derivative^1.02.2.0out of date
 err-derive^0.10.3.1out of date
 fnv^11.0.7up to date
 gltf^0.131.4.1out of date
 hibitset^0.5.10.6.4out of date
 image ⚠️^0.21.00.25.1out of date
 itertools^0.70.13.0out of date
 log^0.4.60.4.21up to date
 mikktspace^0.10.3.0out of date
 sardonyx_animation>=0.0.3N/Aup to date
 sardonyx_assets>=0.0.3N/Aup to date
 sardonyx_core>=0.0.3N/Aup to date
 sardonyx_error>=0.0.3N/Aup to date
 sardonyx_rendy>=0.0.3N/Aup to date
 serde^1.01.0.202up 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.