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 orkhon

Dependencies

(9 total, 6 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 bytes^0.41.10.1out of date
 env_logger^0.6.10.11.8out of date
 error-chain^0.12.10.12.4up to date
 futures-preview^0.3.0-alpha.160.2.2up to date
 log^0.4.60.4.27up to date
 pyo3 ⚠️^0.7.0-alpha.10.25.1out of date
 smallvec ⚠️^0.6.91.15.1out of date
 tract-core^0.3.30.21.13out of date
 tract-tensorflow^0.3.30.21.13out of date

Dev dependencies

(3 total, 1 outdated)

CrateRequiredLatestStatus
 runtime^0.3.0-alpha.40.0.0up to date
 runtime-tokio^0.3.0-alpha.30.0.0up to date
 static_assertions^0.3.21.1.0out of date

Security Vulnerabilities

smallvec: Buffer overflow in SmallVec::insert_many

RUSTSEC-2021-0003

A bug in the SmallVec::insert_many method caused it to allocate a buffer that was smaller than needed. It then wrote past the end of the buffer, causing a buffer overflow and memory corruption on the heap.

This bug was only triggered if the iterator passed to insert_many yielded more items than the lower bound returned from its size_hint method.

The flaw was corrected in smallvec 0.6.14 and 1.6.1, by ensuring that additional space is always reserved for each item inserted. The fix also simplified the implementation of insert_many to use less unsafe code, so it is easier to verify its correctness.

Thank you to Yechan Bae (@Qwaz) and the Rust group at Georgia Tech’s SSLab for finding and reporting this bug.

pyo3: Risk of buffer overflow in `PyString::from_object`

RUSTSEC-2025-0020

PyString::from_object took &str arguments and forwarded them directly to the Python C API without checking for terminating nul bytes. This could lead the Python interpreter to read beyond the end of the &str data and potentially leak contents of the out-of-bounds read (by raising a Python exception containing a copy of the data including the overflow).

In PyO3 0.24.1 this function will now allocate a CString to guarantee a terminating nul bytes. PyO3 0.25 will likely offer an alternative API which takes &CStr arguments.