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 linestring

Dependencies

(11 total, 5 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 approx^0.4.00.5.1out of date
 cgmath^0.18.00.18.0up to date
 fnv^1.0.71.0.7up to date
 itertools^0.10.00.12.1out of date
 mint^0.5.60.5.9up to date
 nalgebra ⚠️^0.24.10.32.4out of date
 num-traits^0.2.140.2.18up to date
 ordered-float^2.1.14.2.0out of date
 rb_tree^0.3.30.5.0out of date
 thiserror^1.0.241.0.58up to date
 vecmath^1.0.01.0.0up to date

Dev dependencies

(2 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 cgmath^0.18.00.18.0up to date
 fltk ⚠️^0.15.21.4.26out of date

Security Vulnerabilities

fltk: Multiple memory safety issues

RUSTSEC-2021-0038

Affected versions contain multiple memory safety issues, such as:

  • Setting a multi label type where an image doesn't exist would lead to a NULL pointer dereference.
  • Setting a window icon using a non-raster image (which FLTK rasterizes lazily) would lead to a NULL dereference.
  • Pixmap constructor would not check for correct pixmaps which could lead to out-of bound reads.

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.