Deps.rs

three 0.4.0

[![dependency status](https://deps.rs/crate/three/0.4.0/status.svg)](https://deps.rs/crate/three/0.4.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 three

Dependencies

(22 total, 17 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 arrayvec^0.40.7.4out of date
 bitflags^12.5.0out of date
 cgmath^0.160.18.0out of date
 derivative^1.02.2.0out of date
 froggy^0.4.40.4.4up to date
 genmesh^0.60.6.2up to date
 gfx^0.17.10.18.3out of date
 gfx_device_gl^0.150.16.2out of date
 gfx_glyph^0.130.17.1out of date
 gfx_window_glutin^0.280.31.0out of date
 gltf^0.11.11.4.0out of date
 glutin^0.190.31.3out of date
 image ⚠️^0.200.25.1out of date
 includedir^0.50.6.0out of date
 itertools^0.80.12.1out of date
 log^0.40.4.21up to date
 mint^0.50.5.9up to date
 obj^0.90.10.2out of date
 phf^0.7.120.11.2out of date
 quick-error^1.22.0.1out of date
 rodio^0.80.17.3out of date
 vec_map^0.80.8.2up to date

Dev dependencies

(3 total, 3 outdated)

CrateRequiredLatestStatus
 env_logger^0.60.11.3out of date
 notify^46.1.1out of date
 rand^0.60.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.