Design/Logic Flaw

The lettre library through 0.10.0-alpha for Rust allows arbitrary sendmail option injection via transport/sendmail/mod.rs...

CVE-2020-28247

The CVE-2020-28247 entry concerns the lettre Rust crate (0.10.0-alpha and earlier) where the sendmail transport (transport/sendmail/mod.rs) is vulnerable to argument injection via forged to addresses. The flaw allows arbitrary options to be passed to the sendmail executable, which in some impleme...

RUSTSEC-2020-0073 Mutable reference with immutable provenance

A mutable reference to a struct was constructed by dereferencing a pointer obtained from slice::asptr. Instead, slice::asmutptr should have been called on the mutable slice argument. The former performs an implicit reborrow as an immutable shared reference which does not allow writing through the...

HiddenBytes (=0.1.0), Rust-wasm (=0.1.0) +726 more potentially affected by CVE-2020-35916 via image (>=0.10.4 <=0.23.10)

image CARGO version =0.10.4, =0.1.0, =0.1.0, =0.0.3, =0.1.0, =1.0.0, =0.1.0, =0.1.0, =0.1.5, =0.1.0, =0.1.0, =0.1.0, =0.3.0 and more Source cves: CVE-2020-35916 Source advisory: OSV:RUSTSEC-2020-0073...

efw (=0.1.0) potentially affected by CVE-2020-36209 via late-static (=0.3.0)

late-static CARGO version =0.3.0 is affected by a known vulnerability. The following packages have a transitive dependency on late-static and may be impacted: - efw =0.1.0 Source cves: CVE-2020-36209 Source advisory: OSV:RUSTSEC-2020-0102...

abra (=0.0.1), abrute (>=0.1.7 <=0.1.9) +702 more potentially affected by CVE-2020-26235 via chrono (>=0.2.16 <=0.4.2)

chrono CARGO version =0.2.16, =0.1.7, =0.1.0, =0.1.0, =0.0.11, =0.7.0, =1.1.0, =0.3.0, =0.1.0, =0.1.0, =0.0.1, =0.1.1, =0.2.0 and more Source cves: CVE-2020-26235 Source advisory: OSV:RUSTSEC-2020-0159...

`Shared` can cause a data race

Shared data structure in model crate implements Send and Sync traits regardless of the inner type. This allows safe Rust code to trigger a data race, which is undefined behavior in Rust. Users are advised to treat Shared as an unsafe type. It should not be used outside of the testing context, and...

AtomicBox<T> implements Send/Sync for any `T: Sized`

Affected versions of this crate implements Send/Sync for AtomicBox without requiring T: Send/T: Sync. This allows to create data races to T: !Sync and send T: !Send to another thread. Such behavior breaks the compile-time thread safety guarantees of Rust, and allows users to incur undefined...

RUSTSEC-2020-0140 `Shared` can cause a data race

Shared data structure in model crate implements Send and Sync traits regardless of the inner type. This allows safe Rust code to trigger a data race, which is undefined behavior in Rust. Users are advised to treat Shared as an unsafe type. It should not be used outside of the testing context, and...

TreeFocus lacks bounds on its Send and Sync traits

Affected versions of im contains TreeFocus that unconditionally implements Send and Sync. This allows a data race in safe Rust code if TreeFocus is extracted from Focus type. Typical users that only use Focus type are not affected...

RUSTSEC-2020-0096 TreeFocus lacks bounds on its Send and Sync traits

Affected versions of im contains TreeFocus that unconditionally implements Send and Sync. This allows a data race in safe Rust code if TreeFocus is extracted from Focus type. Typical users that only use Focus type are not affected...

RUSTSEC-2020-0068 Unexpected panic in multihash `from_slice` parsing code

In versions prior 0.11.3 it's possible to make fromslice panic by feeding it certain malformed input. It's never documented that fromslice and frombytes which wraps it can panic, and its' return type Result suggests otherwise. In practice, fromslice/frombytes is frequently used in networking code...

Unexpected panic in multihash `from_slice` parsing code

In versions prior 0.11.3 it's possible to make fromslice panic by feeding it certain malformed input. It's never documented that fromslice and frombytes which wraps it can panic, and its' return type Result suggests otherwise. In practice, fromslice/frombytes is frequently used in networking code...

Some lock_api lock guard objects can cause data races

Affected versions of lockapi had unsound implementations of the Send or Sync traits for some guard objects, namely: MappedMutexGuard MappedRwLockReadGuard MappedRwLockWriteGuard RwLockReadGuard RwLockWriteGuard These guards could allow data races through types that are not safe to Send across...

AitSar (=0.1.1), AjusteOnuDeReferencia (=0.1.0) +28956 more potentially affected by CVE-2020-35910 +4 more via lock_api (>=0.1.5 <=0.4.14)

lockapi CARGO version =0.1.5, =0.1.0, =0.9.0, =0.0.1-preview.1, =0.1.0-beta.1, =0.1.0, =1.0.0, =1.0.0, =0.1.0, =0.1.4 and more Source cves: CVE-2020-35910, CVE-2020-35911, CVE-2020-35912, CVE-2020-35913, CVE-2020-35914 Source advisory: OSV:RUSTSEC-2020-0070...

Feroxbuster - A Fast, Simple, Recursive Content Discovery Tool Written In Rust

What the heck is a ferox anyway? Ferox is short for Ferric Oxide. Ferric Oxide, simply put, is rust. The name rustbuster was taken, so I decided on a variation. What's it do tho? feroxbuster is a tool designed to perform Forced Browsing. Forced browsing is an attack where the aim is to enumerate...

abrute (>=0.1.7 <=0.1.8), aderyn_core (>=0.0.7 <=0.0.9) +775 more potentially affected by unknown CVE via term_size (>=0.1.1 <=1.0.0-beta.2)

termsize CARGO version =0.1.1, =0.1.7, =0.0.7, =0.0.8, =0.1.0, =0.0.2, =1.0.1, =0.1.0, =1.0.0, =0.1.0, =0.1.0, =0.0.1, =1.2.0, =2.1.1 and more Source cves: unknown CVE Source advisory: OSV:RUSTSEC-2020-0163...

aoaddons (>=0.1.1 <=0.2.0), bls_signature_aggregator (=0.1.0) +2 more potentially affected by unknown CVE via fake_clock (>=0.1.0 <=0.3.1)

fakeclock CARGO version =0.1.0, =0.1.1, =0.6.0, =0.1.0, =1.3.1 Source cves: unknown CVE Source advisory: OSV:RUSTSEC-2020-0065...

`mio` invalidly assumes the memory layout of std::net::SocketAddr

The mio crate has assumed std::net::SocketAddrV4 and std::net::SocketAddrV6 have the same memory layout as the system C representation sockaddr. It has simply casted the pointers to convert the socket addresses to the system representation. The standard library does not say anything about the...

safe-transfers (=0.1.0), sn_transfers (=0.2.0) potentially affected by unknown CVE via safe-nd (>=0.11.7 <=0.9.0)

safe-nd CARGO version =0.11.7, =0.9.0 is affected by a known vulnerability. The following packages have a transitive dependency on safe-nd and may be impacted: - safe-transfers =0.1.0 - sntransfers =0.2.0 Source cves: unknown CVE Source advisory: OSV:RUSTSEC-2020-0063...