Deps.rs

azul-webrender 0.62.2

[![dependency status](https://deps.rs/crate/azul-webrender/0.62.2/status.svg)](https://deps.rs/crate/azul-webrender/0.62.2)

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 azul-webrender

Dependencies

(32 total, 7 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 azul-webrender-api^0.62.00.62.0up to date
 bincode^1.01.3.3up to date
 bitflags^1.22.5.0out of date
 byteorder^1.01.5.0up to date
 core-foundation^0.90.9.4up to date
 core-graphics^0.220.23.2out of date
 core-text^1920.1.0out of date
 cstr^0.20.2.12up to date
 derive_more^0.990.99.17up to date
 dwrote^0.110.11.0up to date
 etagere^0.2.40.2.10up to date
 euclid^0.22.00.22.9up to date
 freetype^0.70.7.2up to date
 fxhash^0.2.10.2.1up to date
 gl-context-loader^0.1.30.1.8up to date
 lazy_static^11.4.0up to date
 libc^0.20.2.154up to date
 log^0.40.4.21up to date
 azul-wr_malloc_size_of^0.0.10.0.1up to date
 malloc_size_of_derive^0.10.1.2up to date
 num-traits^0.20.2.18up to date
 objc^0.20.2.7up to date
 plane-split^0.170.18.0out of date
 png^0.160.17.13out of date
 rayon^11.10.0up to date
 ron^0.6.20.8.1out of date
 serde^1.01.0.200up to date
 smallvec ⚠️^11.13.2maybe insecure
 svg_fmt^0.40.4.2up to date
 time ⚠️^0.10.3.36out of date
 tracy-rs^0.1.20.1.2up to date
 azul-webrender-build^0.0.20.0.2up to date

Dev dependencies

(2 total, 2 outdated)

CrateRequiredLatestStatus
 mozangle^0.3.30.5.1out of date
 rand^0.40.8.5out of date

Security Vulnerabilities

time: Potential segfault in the time crate

RUSTSEC-2020-0071

Impact

Unix-like operating systems may segfault due to dereferencing a dangling pointer in specific circumstances. This requires an environment variable to be set in a different thread than the affected functions. This may occur without the user's knowledge, notably in a third-party library.

The affected functions from time 0.2.7 through 0.2.22 are:

  • time::UtcOffset::local_offset_at
  • time::UtcOffset::try_local_offset_at
  • time::UtcOffset::current_local_offset
  • time::UtcOffset::try_current_local_offset
  • time::OffsetDateTime::now_local
  • time::OffsetDateTime::try_now_local

The affected functions in time 0.1 (all versions) are:

  • at
  • at_utc
  • now

Non-Unix targets (including Windows and wasm) are unaffected.

Patches

Pending a proper fix, the internal method that determines the local offset has been modified to always return None on the affected operating systems. This has the effect of returning an Err on the try_* methods and UTC on the non-try_* methods.

Users and library authors with time in their dependency tree should perform cargo update, which will pull in the updated, unaffected code.

Users of time 0.1 do not have a patch and should upgrade to an unaffected version: time 0.2.23 or greater or the 0.3 series.

Workarounds

A possible workaround for crates affected through the transitive dependency in chrono, is to avoid using the default oldtime feature dependency of the chrono crate by disabling its default-features and manually specifying the required features instead.

Examples:

Cargo.toml:

chrono = { version = "0.4", default-features = false, features = ["serde"] }

chrono = { version = "0.4.22", default-features = false, features = ["clock"] }

Commandline:

cargo add chrono --no-default-features -F clock

Sources:

smallvec: Buffer overflow in SmallVec::insert_many

RUSTSEC-2021-0003

A bug in the SmallVec::insert_many method caused it to allocate a buffer that was smaller than needed. It then wrote past the end of the buffer, causing a buffer overflow and memory corruption on the heap.

This bug was only triggered if the iterator passed to insert_many yielded more items than the lower bound returned from its size_hint method.

The flaw was corrected in smallvec 0.6.14 and 1.6.1, by ensuring that additional space is always reserved for each item inserted. The fix also simplified the implementation of insert_many to use less unsafe code, so it is easier to verify its correctness.

Thank you to Yechan Bae (@Qwaz) and the Rust group at Georgia Tech’s SSLab for finding and reporting this bug.