fix: comments (#6718) #1777
Security advisories found
3 advisories, 7 unmaintained, 3 other
Details
Vulnerabilities
RUSTSEC-2024-0402
Borsh serialization of HashMap is non-canonical
Details | |
---|---|
Package | hashbrown |
Version | 0.15.0 |
URL | rust-lang/hashbrown#576 |
Date | 2024-10-11 |
Patched versions | >=0.15.1 |
Unaffected versions | <0.15.0 |
The borsh serialization of the HashMap did not follow the borsh specification.
It potentially produced non-canonical encodings dependent on insertion order.
It also did not perform canonicty checks on decoding.
This can result in consensus splits and cause equivalent objects to be
considered distinct.
This was patched in 0.15.1.
RUSTSEC-2024-0019
Tokens for named pipes may be delivered after deregistration
Details | |
---|---|
Package | mio |
Version | 0.7.14 |
URL | GHSA-r8w9-5wcg-vfj7 |
Date | 2024-03-04 |
Patched versions | >=0.8.11 |
Unaffected versions | <0.7.2 |
Impact
When using named pipes on Windows, mio will under some circumstances return invalid tokens that correspond to named pipes that have already been deregistered from the mio registry. The impact of this vulnerability depends on how mio is used. For some applications, invalid tokens may be ignored or cause a warning or a crash. On the other hand, for applications that store pointers in the tokens, this vulnerability may result in a use-after-free.
For users of Tokio, this vulnerability is serious and can result in a use-after-free in Tokio.
The vulnerability is Windows-specific, and can only happen if you are using named pipes. Other IO resources are not affected.
Affected versions
This vulnerability has been fixed in mio v0.8.11.
All versions of mio between v0.7.2 and v0.8.10 are vulnerable.
Tokio is vulnerable when you are using a vulnerable version of mio AND you are using at least Tokio v1.30.0. Versions of Tokio prior to v1.30.0 will ignore invalid tokens, so they are not vulnerable.
Workarounds
Vulnerable libraries that use mio can work around this issue by detecting and ignoring invalid tokens.
Technical details
When an IO resource registered with mio has a readiness event, mio delivers that readiness event to the user using a user-specified token. Mio guarantees that when an IO resource is deregistered, then it will never return the token for that IO resource again. However, for named pipes on windows, mio may sometimes deliver the token for a named pipe even though the named pipe has been previously deregistered.
This vulnerability was originally reported in the Tokio issue tracker: tokio-rs/tokio#6369
This vulnerability was fixed in: tokio-rs/mio#1760
Thank you to @rofoun and @radekvit for discovering and reporting this issue.
RUSTSEC-2024-0399
rustls network-reachable panic in
Acceptor::accept
Details | |
---|---|
Package | rustls |
Version | 0.23.13 |
URL | rustls/rustls#2227 |
Date | 2024-11-22 |
Patched versions | >=0.23.18 |
Unaffected versions | >=0.23, <0.23.13,<0.23 |
A bug introduced in rustls 0.23.13 leads to a panic if the received
TLS ClientHello is fragmented. Only servers that use
rustls::server::Acceptor::accept()
are affected.
Servers that use tokio-rustls
's LazyConfigAcceptor
API are affected.
Servers that use tokio-rustls
's TlsAcceptor
API are not affected.
Servers that use rustls-ffi
's rustls_acceptor_accept
API are affected.
Warnings
RUSTSEC-2024-0375
atty
is unmaintained
Details | |
---|---|
Status | unmaintained |
Package | atty |
Version | 0.2.14 |
URL | softprops/atty#57 |
Date | 2024-09-25 |
The maintainer of atty
has published an official notice that the crate is no longer
under development, and that users should instead rely on the functionality in the standard library's IsTerminal
trait.
Alternative(s)
- std::io::IsTerminal - Stable since Rust 1.70.0 and the recommended replacement per the
atty
maintainer. - is-terminal - Standalone crate supporting Rust older than 1.70.0
RUSTSEC-2024-0388
derivative
is unmaintained; consider using an alternative
Details | |
---|---|
Status | unmaintained |
Package | derivative |
Version | 2.2.0 |
URL | mcarton/rust-derivative#117 |
Date | 2024-06-26 |
The derivative
crate is no longer maintained.
Consider using any alternative, for instance:
RUSTSEC-2024-0384
instant
is unmaintained
Details | |
---|---|
Status | unmaintained |
Package | instant |
Version | 0.1.12 |
Date | 2024-09-01 |
This crate is no longer maintained, and the author recommends using the maintained web-time
crate instead.
RUSTSEC-2024-0370
proc-macro-error is unmaintained
Details | |
---|---|
Status | unmaintained |
Package | proc-macro-error |
Version | 1.0.4 |
URL | https://gitlab.com/CreepySkeleton/proc-macro-error/-/issues/20 |
Date | 2024-09-01 |
proc-macro-error's maintainer seems to be unreachable, with no commits for 2 years, no releases pushed for 4 years, and no activity on the GitLab repo or response to email.
proc-macro-error also depends on syn 1.x
, which may be bringing duplicate dependencies into dependant build trees.
Possible Alternative(s)
RUSTSEC-2023-0081
safemem is unmaintained
Details | |
---|---|
Status | unmaintained |
Package | safemem |
Version | 0.3.3 |
URL | https://github.com/abonander/safemem |
Date | 2023-02-14 |
The latest crates.io release was in 2019. The repository has been archived by the author.
Migration
-
safemem::copy_over(slice, src_idx, dest_idx, len);
can be replaced withslice.copy_within(src_idx..src_idx+len, dest_idx);
as ofrust 1.37.0
. -
safemem::write_bytes(slice, byte);
can be replaced withslice.fill(byte);
as ofrust 1.50.0
-
safemem::prepend(slice, vec);
can be replaced withlet old_len = vec.len(); vec.extend_from_slice(slice); vec.rotate_left(old_len);
as of
rust 1.26.0
RUSTSEC-2023-0049
tui
is unmaintained; useratatui
instead
Details | |
---|---|
Status | unmaintained |
Package | tui |
Version | 0.16.0 |
URL | fdehau/tui-rs#654 |
Date | 2023-08-07 |
The tui
crate is no longer maintained.
Consider using the ratatui
crate instead.
RUSTSEC-2024-0320
yaml-rust is unmaintained.
Details | |
---|---|
Status | unmaintained |
Package | yaml-rust |
Version | 0.4.5 |
URL | rustsec/advisory-db#1921 |
Date | 2024-03-20 |
The maintainer seems unreachable.
Many issues and pull requests have been submitted over the years
without any response.
Alternatives
Consider switching to the actively maintained yaml-rust2
fork of the original project:
Crate critical-section
is yanked
No extra details provided.
Crate futures-util
is yanked
No extra details provided.
Crate wasm-bindgen
is yanked
No extra details provided.