Packages
Every advisory and malicious release affecting an open source package on npm, PyPI, Go, Maven, crates.io, NuGet, RubyGems, Packagist or Hex, newest first. See the worst packages this week, or check your lockfile.
- CVE-2019-15544An issue was discovered in the protobuf crate before 2.6.0 for Rust.crates.io · protobuf · fixed in 1.7.5, 2.6.0
- CVE-2019-15545An issue was discovered in the libp2p-core crate before 0.8.1 for Rust.crates.io · libp2p-core · fixed in 0.7.1, 0.8.1
- CVE-2019-15546An issue was discovered in the pancurses crate through 0.16.1 for Rust.crates.io · pancurses
- CVE-2019-15547An issue was discovered in the ncurses crate through 5.99.0 for Rust.crates.io · ncurses
- CVE-2019-15548An issue was discovered in the ncurses crate through 5.99.0 for Rust.crates.io · ncurses
- CVE-2019-15549An issue was discovered in the asn1_der crate before 0.6.2 for Rust.crates.io · asn1_der · fixed in 0.6.2
- CVE-2019-15552An issue was discovered in the libflate crate before 0.1.25 for Rust.crates.io · libflate · fixed in 0.1.25
- CVE-2019-15551An issue was discovered in the smallvec crate before 0.6.10 for Rust.crates.io · smallvec · fixed in 0.6.10
- CVE-2019-15554An issue was discovered in the smallvec crate before 0.6.10 for Rust.crates.io · smallvec · fixed in 0.6.10
- CVE-2019-15553An issue was discovered in the memoffset crate before 0.5.0 for Rust.crates.io · memoffset · fixed in 0.5.0
- CVE-2019-15550An issue was discovered in the simd-json crate before 0.1.15 for Rust.crates.io · simd-json · fixed in 0.1.15
- CVE-2018-21000An issue was discovered in the safe-transmute crate before 0.10.1 for Rust.crates.io · safe-transmute · fixed in 0.10.1
- CVE-2018-20999An issue was discovered in the orion crate before 0.11.2 for Rust.crates.io · orion · fixed in 0.11.2
- CVE-2018-20991An issue was discovered in the smallvec crate before 0.6.3 for Rust.crates.io · smallvec · fixed in 0.6.3, 0.3.4, 0.4.5 and more
- CVE-2018-20990An issue was discovered in the tar crate before 0.4.16 for Rust.crates.io · tar · fixed in 0.4.16
- CVE-2018-20994An issue was discovered in the trust-dns-proto crate before 0.5.0-alpha.3 for Rust.crates.io · trust-dns-proto · fixed in 0.4.3
- CVE-2018-20993An issue was discovered in the yaml-rust crate before 0.4.1 for Rust.crates.io · yaml-rust · fixed in 0.4.1
- CVE-2018-20992An issue was discovered in the claxon crate before 0.4.1 for Rust.crates.io · claxon · fixed in 0.4.1, 0.3.2
- CVE-2017-18587An issue was discovered in the hyper crate before 0.9.18 for Rust.crates.io · hyper · fixed in 0.10.2, 0.9.18
- CVE-2016-10933An issue was discovered in the portaudio crate through 0.7.0 for Rust.crates.io · portaudio
- CVE-2016-10932An issue was discovered in the hyper crate before 0.9.4 for Rust on Windows.crates.io · hyper · fixed in 0.9.4
- CVE-2016-10931An issue was discovered in the openssl crate before 0.9.0 for Rust.crates.io · openssl · fixed in 0.9.0
- CVE-2017-1000430rust-base64 version <= 0.5.1 is vulnerable to a buffer overflow when calculating the size of a buffer to use when encoding base64 using the crates.io · base64 · fixed in 0.5.2
- CVE-2017-1000168sodiumoxide 0.0.13 and older scalarmult() vulnerable to degenerate public keyscrates.io · sodiumoxide · fixed in 0.0.14
- CVE-2015-7558librsvg before 2.40.12 allows context-dependent attackers to cause a denial of service (infinite loop, stack consumption, and application crcrates.io · librsvg · fixed in 2.40.12