Deps.rs

pyo3 0.16.6

[![dependency status](https://deps.rs/crate/pyo3/0.16.6/status.svg)](https://deps.rs/crate/pyo3/0.16.6)

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 pyo3

Dependencies

(15 total, 7 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 anyhow^1.01.0.93up to date
 cfg-if^1.01.0.0up to date
 eyre ⚠️>=0.4, <0.70.6.12maybe insecure
 hashbrown>=0.9, <0.130.15.1out of date
 indexmap>=1.6, <1.82.6.0out of date
 indoc^1.0.32.0.5out of date
 inventory^0.2.00.3.15out of date
 libc^0.2.620.2.162up to date
 num-bigint^0.40.4.6up to date
 num-complex>=0.2, <0.50.4.6up to date
 parking_lot>=0.11, <0.130.12.3up to date
 pyo3-ffi=0.16.60.22.6out of date
 pyo3-macros=0.16.60.22.6out of date
 serde^1.01.0.215up to date
 unindent^0.1.40.2.3out of date

Dev dependencies

(9 total, 4 outdated)

CrateRequiredLatestStatus
 assert_approx_eq^1.1.01.1.0up to date
 criterion^0.3.50.5.1out of date
 proptest^0.10.11.5.0out of date
 rustversion^1.01.0.18up to date
 send_wrapper^0.50.6.0out of date
 serde^1.01.0.215up to date
 serde_json^1.0.611.0.132up to date
 trybuild^1.0.491.0.101up to date
 widestring^0.5.11.1.0out of 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.