Deps.rs

winit 0.19.5

[![dependency status](https://deps.rs/crate/winit/0.19.5/status.svg)](https://deps.rs/crate/winit/0.19.5)

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 winit

Dependencies

(19 total, 9 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 android_glue^0.20.2.3up to date
 backtrace^0.30.3.74up to date
 bitflags^12.6.0out of date
 cocoa^0.18.40.26.0out of date
 core-foundation^0.60.10.0out of date
 core-graphics^0.17.30.24.0out of date
 image ⚠️^0.210.25.4out of date
 lazy_static^11.5.0up to date
 libc^0.20.2.161up to date
 log^0.40.4.22up to date
 objc^0.2.30.2.7up to date
 parking_lot^0.90.12.3out of date
 percent-encoding^2.02.3.1up to date
 raw-window-handle^0.30.6.2out of date
 serde^11.0.214up to date
 smithay-client-toolkit^0.4.30.19.2out of date
 wayland-client^0.210.31.7out of date
 winapi^0.3.60.3.9up to date
 x11-dl^2.18.32.21.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.