Deps.rs

rustfst 0.3.0

[![dependency status](https://deps.rs/crate/rustfst/0.3.0/status.svg)](https://deps.rs/crate/rustfst/0.3.0)

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 rustfst

Dependencies

(9 total, 6 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 bimap^0.3.10.6.3out of date
 bitflags^1.0.42.5.0out of date
 failure^0.10.1.8up to date
 generic-array ⚠️^0.12.01.0.0out of date
 itertools^0.70.12.1out of date
 nom^4.17.1.3out of date
 num-traits^0.20.2.18up to date
 ordered-float ⚠️^14.2.0out of date
 typenum^1.10.01.17.0up to date

Dev dependencies

(5 total, 2 outdated)

CrateRequiredLatestStatus
 counter^0.40.5.7out of date
 rand^0.50.8.5out of date
 serde^1.01.0.198up to date
 serde_derive^1.01.0.198up to date
 serde_json^1.01.0.116up to date

Security Vulnerabilities

ordered-float: ordered_float:NotNan may contain NaN after panic in assignment operators

RUSTSEC-2020-0082

After using an assignment operators such as NotNan::add_assign, NotNan::mul_assign, etc., it was possible for the resulting NotNan value to contain a NaN. This could cause undefined behavior in safe code, because the safe NotNan::cmp method contains internal unsafe code that assumes the value is never NaN. (It could also cause undefined behavior in third-party unsafe code that makes the same assumption, as well as logic errors in safe code.)

This was mitigated starting in version 0.4.0, by panicking if the assigned value is NaN. However, in affected versions from 0.4.0 onward, code that uses the NotNan value during unwinding, or that continues after catching the panic, could still observe the invalid value and trigger undefined behavior.

The flaw is fully corrected in versions 1.1.1 and 2.0.1, by ensuring that the assignment operators panic without modifying the operand, if the result would be NaN.

generic-array: arr! macro erases lifetimes

RUSTSEC-2020-0146

Affected versions of this crate allowed unsoundly extending lifetimes using arr! macro. This may result in a variety of memory corruption scenarios, most likely use-after-free.