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, 1 possibly insecure)

CrateRequiredLatestStatus
 approx^0.30.5.1out of date
 bitflags^12.5.0out of date
 directories^25.0.1out of date
 gfx^0.180.18.3up to date
 gfx_core^0.90.9.2up to date
 gfx_device_gl^0.160.16.2up to date
 gfx_window_glutin^0.300.31.0out of date
 gilrs^0.70.10.6out of date
 glutin^0.200.31.3out of date
 glyph_brush^0.50.7.8out of date
 image^0.220.25.0out of date
 log^0.40.4.21up to date
 lyon^0.131.0.1out of date
 mint^0.50.5.9up to date
 nalgebra ⚠️^0.180.32.5out of date
 rodio^0.90.17.3out of date
 serde^11.0.197up to date
 serde_derive^11.0.197up to date
 smart-default^0.50.7.1out of date
 toml^0.50.8.12out of date
 winit^0.190.29.15out of date
 zip^0.50.6.6out of date

Dev dependencies

(6 total, 4 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 cgmath^0.170.18.0out of date
 chrono ⚠️^0.40.4.37maybe insecure
 fern^0.50.6.2out of date
 rand^0.70.8.5out of date
 skeptic^0.130.13.7up to date
 structopt^0.20.3.26out of date

Security Vulnerabilities

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

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.