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 bender

Dependencies

(17 total, 11 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 atty^0.20.2.14up to date
 blake2 ⚠️^0.7.00.10.6out of date
 clap^2.20.04.5.4out of date
 dirs^15.0.1out of date
 futures^0.10.3.30out of date
 futures-cpupool^0.10.1.8up to date
 itertools^0.8.00.12.1out of date
 pathdiff^0.10.2.1out of date
 semver^0.9.01.0.22out of date
 serde^1.01.0.197up to date
 serde_derive^1.01.0.197up to date
 serde_json^1.01.0.115up to date
 serde_yaml ⚠️^0.70.9.34+deprecatedout of date
 tokio-core^0.1.120.1.18up to date
 tokio-process^0.1.50.2.5out of date
 tokio-timer^0.10.2.13out of date
 typed-arena^1.3.02.0.2out of date

Security Vulnerabilities

serde_yaml: Uncontrolled recursion leads to abort in deserialization

RUSTSEC-2018-0005

Affected versions of this crate did not properly check for recursion while deserializing aliases.

This allows an attacker to make a YAML file with an alias referring to itself causing an abort.

The flaw was corrected by checking the recursion depth.

blake2: HMAC-BLAKE2 algorithms compute incorrect results

RUSTSEC-2019-0019

When used in conjunction with the Hash-based Message Authentication Code (HMAC), the BLAKE2b and BLAKE2s implementations in blake2 crate versions prior to v0.8.1 used an incorrect block size (32-bytes instead of 64-bytes for BLAKE2s, and 64-bytes instead of 128-bytes for BLAKE2b), causing them to miscompute the MacResult.

The v0.8.1 release of the blake2 crate uses the correct block sizes.

Note that this advisory only impacts usage of BLAKE2 with HMAC, and does not impact Digest functionality.