Deps.rs

record-query 1.0.2

[![dependency status](https://deps.rs/crate/record-query/1.0.2/status.svg)](https://deps.rs/crate/record-query/1.0.2)

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 record-query

Dependencies

(26 total, 13 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 ansi_term^0.12.10.12.1up to date
 atty^0.2.130.2.14up to date
 avro-rs^0.6.50.13.0out of date
 csv^1.1.11.3.1up to date
 directories^2.0.26.0.0out of date
 dtoa^0.4.41.0.10out of date
 env_logger^0.7.10.11.8out of date
 failure^0.1.60.1.8up to date
 glob^0.3.00.3.2up to date
 itoa^0.4.41.0.15out of date
 log^0.4.80.4.27up to date
 nix^0.15.00.30.1out of date
 ordered-float ⚠️^1.0.25.0.0out of date
 pest^2.1.22.8.1up to date
 protobuf ⚠️^2.8.13.7.2out of date
 rmp^0.8.80.8.14up to date
 rmpv^0.4.21.3.0out of date
 serde^1.0.1021.0.219up to date
 serde-hjson^0.9.11.1.0out of date
 serde-protobuf^0.8.10.8.2up to date
 serde_cbor^0.10.20.11.2out of date
 serde_json^1.0.411.0.140up to date
 serde_yaml^0.8.110.9.34+deprecatedout of date
 structopt^0.3.40.3.26up to date
 toml^0.5.50.8.23out of date
 yaml-rust^0.4.30.4.5up 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.

protobuf: Crash due to uncontrolled recursion in protobuf crate

RUSTSEC-2024-0437

Affected version of this crate did not properly parse unknown fields when parsing a user-supplied input.

This allows an attacker to cause a stack overflow when parsing the mssage on untrusted data.