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 qjs

Dependencies

(7 total, 3 outdated)

CrateRequiredLatestStatus
 log^0.40.4.22up to date
 failure^0.10.1.8up to date
 bitflags^1.12.6.0out of date
 foreign-types^0.40.5.0out of date
 lazy_static^1.31.5.0up to date
 cstr^0.10.2.12out of date
 proc-macro-hack^0.50.5.20+deprecatedup to date

Dev dependencies

(8 total, 3 outdated)

CrateRequiredLatestStatus
 pretty_env_logger^0.30.5.0out of date
 cfg-if^0.11.0.0out of date
 structopt^0.30.3.26up to date
 tempfile^3.13.14.0up to date
 cc^1.01.2.1up to date
 platforms^0.23.5.0out of date
 cfile^0.50.5.1up to date
 libc^0.20.2.164up to date

Crate qjs-sys

Dependencies

(2 total, 1 outdated)

CrateRequiredLatestStatus
 cfg-if^0.11.0.0out of date
 lazy_static^1.31.5.0up to date

Build dependencies

(7 total, 2 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 failure^0.10.1.8up to date
 lazy_static^1.31.5.0up to date
 regex ⚠️^11.11.1maybe insecure
 cc^1.01.2.1up to date
 bindgen^0.510.70.1out of date
 rust-lzma^0.40.6.0out of date
 tar ⚠️^0.40.4.43maybe insecure

Crate qjs-derive

Dependencies

(5 total, 1 outdated)

CrateRequiredLatestStatus
 log^0.40.4.22up to date
 stderrlog^0.40.6.0out of date
 proc-macro2^1.01.0.92up to date
 quote^1.01.0.37up to date
 proc-macro-hack^0.50.5.20+deprecatedup to date

Crate qjs-derive-support

Dependencies

(5 total, 1 outdated)

CrateRequiredLatestStatus
 log^0.40.4.22up to date
 if_chain^1.01.0.2up to date
 proc-macro2^1.01.0.92up to date
 syn^1.02.0.89out of date
 quote^1.01.0.37up to date

Dev dependencies

(2 total, 1 outdated)

CrateRequiredLatestStatus
 pretty_env_logger^0.30.5.0out of date
 matches^0.10.1.10up 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!

regex: Regexes with large repetitions on empty sub-expressions take a very long time to parse

RUSTSEC-2022-0013

The Rust Security Response WG was notified that the regex crate did not properly limit the complexity of the regular expressions (regex) it parses. An attacker could use this security issue to perform a denial of service, by sending a specially crafted regex to a service accepting untrusted regexes. No known vulnerability is present when parsing untrusted input with trusted regexes.

This issue has been assigned CVE-2022-24713. The severity of this vulnerability is "high" when the regex crate is used to parse untrusted regexes. Other uses of the regex crate are not affected by this vulnerability.

Overview

The regex crate features built-in mitigations to prevent denial of service attacks caused by untrusted regexes, or untrusted input matched by trusted regexes. Those (tunable) mitigations already provide sane defaults to prevent attacks. This guarantee is documented and it's considered part of the crate's API.

Unfortunately a bug was discovered in the mitigations designed to prevent untrusted regexes to take an arbitrary amount of time during parsing, and it's possible to craft regexes that bypass such mitigations. This makes it possible to perform denial of service attacks by sending specially crafted regexes to services accepting user-controlled, untrusted regexes.

Affected versions

All versions of the regex crate before or equal to 1.5.4 are affected by this issue. The fix is include starting from regex 1.5.5.

Mitigations

We recommend everyone accepting user-controlled regexes to upgrade immediately to the latest version of the regex crate.

Unfortunately there is no fixed set of problematic regexes, as there are practically infinite regexes that could be crafted to exploit this vulnerability. Because of this, we do not recommend denying known problematic regexes.

Acknowledgements

We want to thank Addison Crump for responsibly disclosing this to us according to the Rust security policy, and for helping review the fix.

We also want to thank Andrew Gallant for developing the fix, and Pietro Albini for coordinating the disclosure and writing this advisory.