RustSec

Growth in the @RustSec security advisory database year-over-year throughout its 6-year history

RT @github: Rust is the fastest growing language on GitHub, and GitHub’s supply chain security features now help keep your Rust projects secure 🔒

RT @llogiq: Comparing Rust supply chain safety tools

RT @rustlang: A malicious crate was uploaded to targeting GitLab CI environments. Read more on the security advisory:

RT @rustlang: The regex crate is vulnerable to denial of service attacks when parsing untrusted regexes (CVE-2022-24713). We released version 1.5.5, fixing the issue. Read the advisory:

RT @rustlang: The std::fs::remove_dir_all function in the Rust standard library is vulnerable to a race condition (CVE-2022-21658). We will release Rust 1.58.1 with the fix later today. Read the advisory:

This is the first year that we've ever seen fewer advisories filed than the previous year! One reason why is because the bulk of advisories for vulnerabilities discovered by the Rudra static code analyzer were filed in 2020

We are very happy to share that Rudra received a distinguished artifact award in SOSP 2021!

RT @rustlang: We have a security advisory for rustc today: We will have a 1.56.1 release out soon.

The web site now features severity information for each security advisory

Heads up Rustsceans! You might have recently gotten a security vulnerability notification for RUSTSEC-2020-0071: a potential segfault impacting `time` v0.1 (cont’d)

This isn’t a false positive, but rather a case where the advisory has been updated to include earlier versions of the `time` crate. Unfortunately the fix is only in `time` v0.2, and it’s unclear if it can be backported to v0.1 due to API constraints.

Unfortunately we don’t have clear guidance for what to do. It impacts several major ecosystem crates including `chrono`. For the latest information, see the upstream issue on `time`:

RT @Kate_Catlin: My team's first release since I joined GitHub is out today, and my first GitHub blog is live! Thanks so much to the @RustSec community for collaborating to bring curated Rust security advisories to the GitHub Advisory Database!

Growth in the @RustSec security advisory database year-over-year throughout its 5-year history

Why so much @RustSec growth in 2020? Part of it is more @rustlang adoption and a growing ecosystem. 2020 also saw more Rust security/vulnerability research including hardening efforts like Safety Dance as well as growth in academic security research.

Introducing `auditable`: audit compiled @rustlang binaries against security advisories in the @RUSTSEC database:

RUSTSEC-2020-0036: failure is officially deprecated/unmaintained

RT @rustlang: The Rust team was notified of a vulnerability affecting API tokens generation and storage, and out of aboundance of precaution we revoked all existing tokens. Learn more on the advisory:

We've posted a retrospective on RUSTSEC advisories filed in April 2020: - rusqlite - os_str_bytes - flatbuffers - fake-static - plutonium

cargo-audit v0.12.0 is out with some minor fixes, including git2 crate updates which should make it easier to install: