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.
yore(16 total, 8 outdated, 3 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| actix-web ⚠️ | ^0.7 | 4.10.2 | out of date |
| chrono ⚠️ | ^0.4 | 0.4.40 | maybe insecure |
| directories | ^1.0 | 6.0.0 | out of date |
| futures | ^0.1.25 | 0.3.31 | out of date |
| image ⚠️ | ^0.20.0 | 0.25.6 | out of date |
| jpeg-decoder | ^0.1.15 | 0.3.1 | out of date |
| memmap | ^0.7 | 0.7.0 | up to date |
| kamadak-exif | ^0.3 | 0.6.1 | out of date |
| rayon | ^1.0 | 1.10.0 | up to date |
| serde | ^1.0 | 1.0.219 | up to date |
| serde_derive | ^1.0 | 1.0.219 | up to date |
| serde_json | ^1.0 | 1.0.140 | up to date |
| structopt | ^0.2 | 0.3.26 | out of date |
| tinyfiledialogs | ^3.3.5 | 3.9.1 | up to date |
| walkdir | ^2 | 2.5.0 | up to date |
| web-view | ^0.2.1 | 0.7.3 | out of date |
(1 total, all up-to-date)
| Crate | Required | Latest | Status |
|---|---|---|---|
| tempfile | ^3 | 3.19.1 | up to date |
actix-web: Multiple memory safety issuesAffected versions contain multiple memory safety issues, such as:
Send marker trait to objects that cannot be safely sent between threadsThis may result in a variety of memory corruption scenarios, most likely use-after-free.
A significant refactoring effort has been conducted to resolve these issues.
image: Flaw in interface may drop uninitialized instance of arbitrary typesAffected versions of this crate would call Vec::set_len on an uninitialized
vector with user-provided type parameter, in an interface of the HDR image
format decoder. They would then also call other code that could panic before
initializing all instances.
This could run Drop implementations on uninitialized types, equivalent to use-after-free, and allow an attacker arbitrary code execution.
Two different fixes were applied. It is possible to conserve the interface by
ensuring proper initialization before calling Vec::set_len. Drop is no longer
called in case of panic, though.
Starting from version 0.22, a breaking change to the interface requires
callers to pre-allocate the output buffer and pass a mutable slice instead,
avoiding all unsafe code.
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.