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 buildkite-jobify

Dependencies

(25 total, 1 outdated, 4 possibly insecure)

CrateRequiredLatestStatus
 anyhow^1.01.0.57up to date
 app_dirs2^2.32.4.0up to date
 base64^0.130.13.0up to date
 bytes^1.01.1.0up to date
 crossbeam^0.80.8.1up to date
 flate2^1.01.0.23up to date
 futures^0.30.3.21up to date
 graphql_client^0.100.10.0up to date
 http^0.20.2.7up to date
 lru_time_cache^0.110.11.11up to date
 openssl ⚠️^0.100.10.40maybe insecure
 reqwest^0.110.11.10up to date
 serde^1.01.0.137up to date
 serde_json^1.01.0.81up to date
 serde_yaml ⚠️^0.80.8.24maybe insecure
 tar ⚠️^0.40.4.38maybe insecure
 toml^0.50.5.9up to date
 structopt^0.30.3.26up to date
 tame-oauth^0.70.7.0up to date
 tracing^0.10.1.34up to date
 tracing-subscriber^0.30.3.11up to date
 twox-hash^1.61.6.3up to date
 uuid^0.81.0.0out of date
 tokio ⚠️^1.01.18.2maybe insecure
 k8s-openapi^0.140.14.0up to date

Security Vulnerabilities

serde_yaml: Uncontrolled recursion leads to abort in deserialization

RUSTSEC-2018-0005

Affected versions of this crate did not properly check for recursion while deserializing aliases.

This allows an attacker to make a YAML file with an alias referring to itself causing an abort.

The flaw was corrected by checking the recursion depth.

openssl: Use after free in CMS Signing

RUSTSEC-2018-0010

Affected versions of the OpenSSL crate used structures after they'd been freed.

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!

tokio: Data race when sending and receiving after closing a `oneshot` channel

RUSTSEC-2021-0124

If a tokio::sync::oneshot channel is closed (via the oneshot::Receiver::close method), a data race may occur if the oneshot::Sender::send method is called while the corresponding oneshot::Receiver is awaited or calling try_recv.

When these methods are called concurrently on a closed channel, the two halves of the channel can concurrently access a shared memory location, resulting in a data race. This has been observed to cause memory corruption.

Note that the race only occurs when both halves of the channel are used after the Receiver half has called close. Code where close is not used, or where the Receiver is not awaited and try_recv is not called after calling close, is not affected.

See tokio#4225 for more details.