This project contains known security vulnerabilities. Find detailed information at the bottom.

Crate ggez

Dependencies

(22 total, 15 outdated, 1 insecure)

CrateRequiredLatestStatus
 approx^0.30.5.1out of date
 bitflags^12.13.2out of date
 directories^26.0.0out 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.11.2out of date
 glutin^0.200.32.3out of date
 glyph_brush^0.50.7.12out of date
 image^0.210.25.10out of date
 log^0.40.4.34up to date
 lyon^0.131.0.19out of date
 mint^0.50.5.9up to date
 nalgebra ⚠️^0.180.35.0insecure
 rodio^0.90.22.2out of date
 serde^11.0.229up to date
 serde_derive^11.0.229up to date
 smart-default^0.50.7.1out of date
 toml^0.51.1.6+spec-1.1.0out of date
 winit^0.190.30.13out of date
 zip^0.58.6.0out of date

Dev dependencies

(6 total, 4 outdated)

CrateRequiredLatestStatus
 cgmath^0.170.18.0out of date
 chrono^0.40.4.45up to date
 fern^0.50.7.1out of date
 rand^0.70.10.3out of date
 skeptic^0.130.13.7up to date
 structopt^0.20.3.26out of date

Security Vulnerabilities

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.