This project contains known security vulnerabilities. Find detailed information at the bottom.
nanopub(10 total, 1 outdated, 1 insecure, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| base64 | ^0.22 | 0.22.1 | up to date |
| oxrdf | ^0.3 | 0.3.3 | up to date |
| oxttl | ^0.2 | 0.2.3 | up to date |
| oxjsonld | ^0.2 | 0.2.5 | up to date |
| regex | ^1.10 | 1.12.4 | up to date |
| serde | ^1.0 | 1.0.228 | up to date |
| chrono ⚠️ | ^0.4 | 0.4.45 | maybe insecure |
| rsa ⚠️ | ^0.9 | 0.9.10 | insecure |
| getrandom | ^0.3 | 0.4.3 | out of date |
| reqwest | ^0.13 | 0.13.4 | up to date |
nanopub-cli(2 total, all up-to-date)
| Crate | Required | Latest | Status |
|---|---|---|---|
| clap | ^4.5 | 4.6.1 | up to date |
| clap_complete | ^4.5 | 4.6.7 | up to date |
nanopub-sign(2 total, 2 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| pyo3 ⚠️ | ^0.28 | 0.29.0 | out of date |
| pythonize | ^0.28 | 0.29.0 | out of date |
nanopub-js(8 total, 2 outdated)
| Crate | Required | Latest | Status |
|---|---|---|---|
| wasm-bindgen | ^0.2 | 0.2.126 | up to date |
| wasm-bindgen-futures | ^0.4 | 0.4.76 | up to date |
| wasm-bindgen-derive | ^0.3 | 0.4.0 | out of date |
| js-sys | ^0.3 | 0.3.103 | up to date |
| serde | ^1.0 | 1.0.228 | up to date |
| serde-wasm-bindgen | ^0.6 | 0.6.5 | up to date |
| getrandom | ^0.3 | 0.4.3 | out of date |
| console_error_panic_hook | ^0.1 | 0.1.7 | up to date |
(1 total, all up-to-date)
| Crate | Required | Latest | Status |
|---|---|---|---|
| wasm-bindgen-test | ^0.3 | 0.3.76 | up to date |
chrono: Potential segfault in `localtime_r` invocationsUnix-like operating systems may segfault due to dereferencing a dangling pointer in specific circumstances. This requires an environment variable to be set in a different thread than the affected functions. This may occur without the user's knowledge, notably in a third-party library.
No workarounds are known.
rsa: Marvin Attack: potential key recovery through timing sidechannelsDue to a non-constant-time implementation, information about the private key is leaked through timing information which is observable over the network. An attacker may be able to use that information to recover the key.
No patch is yet available, however work is underway to migrate to a fully constant-time implementation.
The only currently available workaround is to avoid using the rsa crate in settings where attackers are able to observe timing information, e.g. local use on a non-compromised computer is fine.
This vulnerability was discovered as part of the "Marvin Attack", which revealed several implementations of RSA including OpenSSL had not properly mitigated timing sidechannel attacks.
pyo3: Out-of-bounds read in `nth` / `nth_back` for `PyList` and `PyTuple` iteratorsPyO3 0.24.0 added optimized implementations of Iterator::nth and
DoubleEndedIterator::nth_back for the BoundListIterator and
BoundTupleIterator types. These implementations computed the target index
using unchecked usize addition (index + n) before bounds-checking against
the sequence length, then read the element via get_item_unchecked.
In nth methods, a sufficiently large n (combined with a non-zero internal
index) could cause the addition to overflow and wrap around, producing a small
"target index" that passed the bounds check and enabling reads at the front
of the list or tuple of elements previously yielded by the iterator.
In nth_back methods, a sufficiently large n could cause underflow in a
similar fashion, however would instead allow reads of arbitrary memory past
the end of the list or tuple storage.
PyO3 0.29.0 has corrected these methods to use checked arithmetic at the positions which could be at risk of overflow.
pyo3: Missing `Sync` bound on `PyCFunction::new_closure` closuresPyCFunction::new_closure (and the temporary new_closure_bound complement in
the 0.21–0.22 series) required the supplied closure to be Send + 'static but
not Sync. The resulting PyCFunction is a Python callable that can be
invoked from any Python thread, which means the closure may be called
concurrently from multiple threads, and needs a Sync bound to prevent
possible data races.
The problem exists under all Python versions but is particularly vulnerable under
the newer free-threaded Python variant, which do not have serial execution
imposed by the Global Interpreter Lock. Under releases protected by the GIL,
the ability to "detach" from the Python interpreter temporarily inside the closure
(e.g. by Python::detach) makes it possible for interleaved and/or concurrent
execution of various portions of the closure.
PyO3 0.29.0 added a Sync bound to close this thread-safety bug.