Deps.rs

fastobo 0.8.3

[![dependency status](https://deps.rs/crate/fastobo/0.8.3/status.svg)](https://deps.rs/crate/fastobo/0.8.3)

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 fastobo

Dependencies

(12 total, 6 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 crossbeam-channel^0.40.5.12out of date
 err-derive^0.2.00.3.1out of date
 fastobo-derive-internal^0.8.30.15.2out of date
 fastobo-syntax^0.3.80.8.1out of date
 lazy_static^1.4.01.4.0up to date
 memchr^2.2.12.7.2up to date
 num_cpus^1.12.01.16.0up to date
 opaque_typedef^0.0.50.0.5up to date
 opaque_typedef_macros^0.0.50.0.5up to date
 ordered-float ⚠️^1.0.24.2.0out of date
 pest=2.1.22.7.9out of date
 url^2.1.02.5.0up to date

Dev dependencies

(7 total, 5 outdated)

CrateRequiredLatestStatus
 isbn^0.2.00.2.0up to date
 lazy_static^1.3.01.4.0up to date
 obofoundry^0.4.00.10.0out of date
 pretty_assertions^0.6.11.4.0out of date
 serde_yaml^0.8.80.9.34+deprecatedout of date
 textwrap-macros^0.2.00.3.0out of date
 ureq^0.11.02.9.6out of 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.