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.
miniserve(26 total, 18 outdated, 3 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| actix | ^0.7 | 0.13.3 | out of date |
| actix-web ⚠️ | ^0.7 | 4.5.1 | out of date |
| alphanumeric-sort | ^1.0.6 | 1.5.3 | up to date |
| base64 | ^0.10 | 0.22.0 | out of date |
| bytes | ^0.4.12 | 1.6.0 | out of date |
| bytesize | ^1.0.0 | 1.3.0 | up to date |
| chrono ⚠️ | ^0.4.7 | 0.4.38 | maybe insecure |
| chrono-humanize | ^0.0.11 | 0.2.3 | out of date |
| clap | ^2.29 | 4.5.4 | out of date |
| failure | ^0.1.5 | 0.1.8 | up to date |
| futures | ^0.1.28 | 0.3.30 | out of date |
| hex | ^0.3.2 | 0.4.3 | out of date |
| htmlescape | ^0.3.1 | 0.3.1 | up to date |
| libflate | ^0.1.24 | 2.0.0 | out of date |
| log | ^0.4.6 | 0.4.21 | up to date |
| maud | ^0.20.0 | 0.26.0 | out of date |
| nanoid | ^0.2.0 | 0.4.0 | out of date |
| percent-encoding | ^1.0.1 | 2.3.1 | out of date |
| serde | ^1.0.94 | 1.0.198 | up to date |
| sha2 | ^0.8.0 | 0.10.8 | out of date |
| simplelog | ^0.6 | 0.12.2 | out of date |
| structopt | ^0.2.18 | 0.3.26 | out of date |
| strum | ^0.15.0 | 0.26.2 | out of date |
| strum_macros | ^0.15.0 | 0.26.2 | out of date |
| tar ⚠️ | ^0.4.25 | 0.4.40 | maybe insecure |
| yansi | ^0.5 | 1.0.1 | out of date |
(7 total, 7 outdated)
| Crate | Required | Latest | Status |
|---|---|---|---|
| assert_cmd | ^0.11 | 2.0.14 | out of date |
| assert_fs | ^0.11 | 1.1.1 | out of date |
| port_check | ^0.1 | 0.2.1 | out of date |
| pretty_assertions | ^0.6 | 1.4.0 | out of date |
| reqwest | ^0.9 | 0.12.3 | out of date |
| rstest | ^0.3 | 0.19.0 | out of date |
| select | ^0.4 | 0.6.0 | out of 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.
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.
tar: Links in archive can create arbitrary directoriesWhen unpacking a tarball that contains a symlink the tar crate may create
directories outside of the directory it's supposed to unpack into.
The function errors when it's trying to create a file, but the folders are already created at this point.
use std::{io, io::Result};
use tar::{Archive, Builder, EntryType, Header};
fn main() -> Result<()> {
let mut buf = Vec::new();
{
let mut builder = Builder::new(&mut buf);
// symlink: parent -> ..
let mut header = Header::new_gnu();
header.set_path("symlink")?;
header.set_link_name("..")?;
header.set_entry_type(EntryType::Symlink);
header.set_size(0);
header.set_cksum();
builder.append(&header, io::empty())?;
// file: symlink/exploit/foo/bar
let mut header = Header::new_gnu();
header.set_path("symlink/exploit/foo/bar")?;
header.set_size(0);
header.set_cksum();
builder.append(&header, io::empty())?;
builder.finish()?;
};
Archive::new(&*buf).unpack("demo")
}
This has been fixed in https://github.com/alexcrichton/tar-rs/pull/259 and is
published as tar 0.4.36. Thanks to Martin Michaelis (@mgjm) for discovering
and reporting this, and Nikhil Benesch (@benesch) for the fix!