Deps.rs

ascom-alpaca 1.0.0-beta.3

[![dependency status](https://deps.rs/crate/ascom-alpaca/1.0.0-beta.3/status.svg)](https://deps.rs/crate/ascom-alpaca/1.0.0-beta.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 ascom-alpaca

Dependencies

(33 total, 13 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 async-fn-stream^0.2.00.3.0out of date
 async-trait^0.1.770.1.89up to date
 axum^0.7.40.8.4out of date
 bytemuck^1.14.01.23.2up to date
 bytes^1.5.01.10.1up to date
 custom_debug^0.5.10.6.2out of date
 default-net^0.21.00.22.0out of date
 eyre ⚠️^0.6.110.6.12maybe insecure
 futures^0.3.300.3.31up to date
 http^1.0.01.3.1up to date
 indexmap^2.1.02.11.4up to date
 macro_rules_attribute^0.2.00.2.2up to date
 mediatype^0.19.170.20.0out of date
 mime^0.3.170.3.17up to date
 ndarray^0.15.60.16.1out of date
 net-literals^0.2.00.2.0up to date
 num_enum^0.7.20.7.4up to date
 once_cell^1.19.01.21.3up to date
 rand^0.8.50.9.2out of date
 reqwest^0.11.230.12.23out of date
 sailfish^0.8.30.10.0out of date
 serde^1.0.1951.0.225up to date
 serde-ndim^1.1.02.1.0out of date
 serde_json^1.0.1111.0.145up to date
 serde_plain^1.0.21.0.2up to date
 serde_repr^0.1.180.1.20up to date
 socket2^0.5.50.6.0out of date
 thiserror^1.0.562.0.16out of date
 time^0.3.310.3.43up to date
 tokio^1.35.11.47.1up to date
 tracing^0.1.400.1.41up to date
 tracing-futures^0.2.50.2.5up to date
 windows-sys^0.52.00.61.0out of date

Dev dependencies

(13 total, 5 outdated)

CrateRequiredLatestStatus
 bayer^0.1.50.1.5up to date
 color-eyre^0.6.20.6.5up to date
 criterion^0.5.10.7.0out of date
 ctor^0.2.60.5.0out of date
 eframe^0.25.00.32.3out of date
 ndarray^0.15.60.16.1out of date
 nokhwa^0.10.40.10.9up to date
 parking_lot^0.12.10.12.4up to date
 serial_test^3.0.03.2.0up to date
 time^0.3.310.3.43up to date
 tracing-error^0.2.00.2.1up to date
 tracing-forest^0.1.60.2.0out of date
 tracing-subscriber^0.3.180.3.20up to date

Security Vulnerabilities

eyre: Parts of Report are dropped as the wrong type during downcast

RUSTSEC-2024-0021

In affected versions, after a Report is constructed using wrap_err or wrap_err_with to attach a message of type D onto an error of type E, then using downcast to recover ownership of either the value of type D or the value of type E, one of two things can go wrong:

  • If downcasting to E, there remains a value of type D to be dropped. It is incorrectly "dropped" by running E's drop behavior, rather than D's. For example if D is &str and E is std::io::Error, there would be a call of std::io::Error::drop in which the reference received by the Drop impl does not refer to a valid value of type std::io::Error, but instead to &str.

  • If downcasting to D, there remains a value of type E to be dropped. When D and E do not happen to be the same size, E's drop behavior is incorrectly executed in the wrong location. The reference received by the Drop impl may point left or right of the real E value that is meant to be getting dropped.

In both cases, when the Report contains an error E that has nontrivial drop behavior, the most likely outcome is memory corruption.

When the Report contains an error E that has trivial drop behavior (for example a Utf8Error) but where D has nontrivial drop behavior (such as String), the most likely outcome is that downcasting to E would leak D.