ggez 0.5.0-rc.2

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 `ggez`

Dependencies

(22 total, 15 outdated, 2 possibly insecure)

Crate	Required	Latest	Status
approx	`^0.3`	`0.5.1`	out of date
bitflags	`^1.0`	`2.5.0`	out of date
directories	`^1.0.2`	`5.0.1`	out of date
gfx	`^0.18`	`0.18.3`	up to date
gfx_core	`^0.9`	`0.9.2`	up to date
gfx_device_gl	`^0.16`	`0.16.2`	up to date
gfx_window_glutin	`^0.30`	`0.31.0`	out of date
gilrs	`^0.7`	`0.10.6`	out of date
glutin	`^0.20`	`0.31.3`	out of date
glyph_brush	`^0.4`	`0.7.8`	out of date
image ⚠️	`^0.21`	`0.25.1`	out of date
log	`^0.4`	`0.4.21`	up to date
lyon	`^0.13`	`1.0.1`	out of date
mint	`^0.5`	`0.5.9`	up to date
nalgebra ⚠️	`^0.18`	`0.32.5`	out of date
rodio	`^0.8`	`0.17.3`	out of date
serde	`^1`	`1.0.198`	up to date
serde_derive	`^1`	`1.0.198`	up to date
smart-default	`^0.5`	`0.7.1`	out of date
toml	`^0.5`	`0.8.12`	out of date
winit	`^0.19`	`0.29.15`	out of date
zip	`^0.5`	`1.1.1`	out of date

Dev dependencies

(6 total, 4 outdated, 1 possibly insecure)

Crate	Required	Latest	Status
cgmath	`^0.17`	`0.18.0`	out of date
chrono ⚠️	`^0.4`	`0.4.38`	maybe insecure
fern	`^0.5`	`0.6.2`	out of date
rand	`^0.6`	`0.8.5`	out of date
skeptic	`^0.13`	`0.13.7`	up to date
structopt	`^0.2`	`0.3.26`	out 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.

`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

time-rs/time#293

`nalgebra`: VecStorage Deserialize Allows Violation of Length Invariant

RUSTSEC-2021-0070

The Deserialize implementation for VecStorage did not maintain the invariant that the number of elements must equal nrows * ncols. Deserialization of specially crafted inputs could allow memory access beyond allocation of the vector.

This flaw was introduced in v0.11.0 (086e6e) due to the addition of an automatically derived implementation of Deserialize for MatrixVec. MatrixVec was later renamed to VecStorage in v0.16.13 (0f66403) and continued to use the automatically derived implementation of Deserialize.

This flaw was corrected in commit 5bff536 by returning an error during deserialization if the number of elements does not exactly match the expected size.