Deps.rs

stevebob / gws

[![dependency status](https://deps.rs/repo/github/stevebob/gws/status.svg)](https://deps.rs/repo/github/stevebob/gws)

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 gws

Dependencies

(11 total, 9 outdated)

CrateRequiredLatestStatus
 rand^0.60.8.5out of date
 wfc^0.80.10.7out of date
 line_2d^0.10.5.3out of date
 serde^1.01.0.198up to date
 grid_2d^0.120.15.3out of date
 coord_2d^0.20.3.6out of date
 direction^0.170.18.1out of date
 shadowcast^0.50.8.1out of date
 rgb24^0.10.3.1out of date
 hashbrown^0.10.14.3out of date
 grid_search^0.150.15.1up to date

Crate gws_prototty

Dependencies

(6 total, 5 outdated)

CrateRequiredLatestStatus
 serde^1.01.0.198up to date
 prototty^0.270.29.0out of date
 rand^0.60.8.5out of date
 rand_isaac^0.10.3.0out of date
 direction^0.170.18.1out of date
 grid_2d^0.120.15.3out of date

Crate gws_native

Dependencies

(2 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 simon^0.20.4.0out of date
 whoami ⚠️^0.51.5.1out of date

Crate gws_glutin

Dependencies

(2 total, 1 outdated)

CrateRequiredLatestStatus
 prototty_glutin^0.270.27.0up to date
 simon^0.20.4.0out of date

Crate gws_unix

Dependencies

(1 total, all up-to-date)

CrateRequiredLatestStatus
 prototty_unix^0.270.27.0up to date

Crate gws_wasm

Dependencies

(2 total, all up-to-date)

CrateRequiredLatestStatus
 prototty_wasm^0.270.27.0up to date
 wasm-bindgen^0.20.2.92up to date

Crate image-to-text

Dependencies

(2 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 image ⚠️^0.210.25.1out of date
 simon^0.20.4.0out 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.

whoami: Stack buffer overflow with whoami on several Unix platforms

RUSTSEC-2024-0020

With versions of the whoami crate >= 0.5.3 and < 1.5.0, calling any of these functions leads to an immediate stack buffer overflow on illumos and Solaris:

  • whoami::username
  • whoami::realname
  • whoami::username_os
  • whoami::realname_os

With versions of the whoami crate >= 0.5.3 and < 1.0.1, calling any of the above functions also leads to a stack buffer overflow on these platforms:

  • Bitrig
  • DragonFlyBSD
  • FreeBSD
  • NetBSD
  • OpenBSD

This occurs because of an incorrect definition of the passwd struct on those platforms.

As a result of this issue, denial of service and data corruption have both been observed in the wild. The issue is possibly exploitable as well.

This vulnerability also affects other Unix platforms that aren't Linux or macOS.

This issue has been addressed in whoami 1.5.0.

For more information, see this GitHub issue.