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.
serde_qs(8 total, 1 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| actix-web | ^4.0 | 4.5.1 | up to date |
| axum | ^0.6 | 0.7.5 | out of date |
| futures | ^0.3 | 0.3.30 | up to date |
| percent-encoding | ^2.1 | 2.3.1 | up to date |
| serde | ^1.0 | 1.0.198 | up to date |
| thiserror | ^1.0 | 1.0.59 | up to date |
| tracing | ^0.1 | 0.1.40 | up to date |
| warp ⚠️ | ^0.3 | 0.3.7 | maybe insecure |
(6 total, 1 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| chrono ⚠️ | ^0.4 | 0.4.38 | maybe insecure |
| csv | ^1.1 | 1.3.0 | up to date |
| rand | ^0.8 | 0.8.5 | up to date |
| serde_derive | ^1.0 | 1.0.198 | up to date |
| serde_urlencoded | ^0.7 | 0.7.1 | up to date |
| serde_with | ^2.0 | 3.8.0 | out of 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.
warp: Improper validation of Windows paths could lead to directory traversal attackPath resolution in warp::filters::fs::dir didn't correctly validate Windows paths
meaning paths like /foo/bar/c:/windows/web/screen/img101.png would be allowed
and respond with the contents of c:/windows/web/screen/img101.png. Thus users
could potentially read files anywhere on the filesystem.
This only impacts Windows. Linux and other unix likes are not impacted by this.