Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

build(deps): Bump testcontainers from 0.21.1 to 0.22.0 #900

Merged
merged 1 commit into from
Sep 2, 2024

build(deps): Bump testcontainers from 0.21.1 to 0.22.0

1a6dcb8
Select commit
Loading
Failed to load commit list.
Sign in for the full log view
Merged

build(deps): Bump testcontainers from 0.21.1 to 0.22.0 #900

build(deps): Bump testcontainers from 0.21.1 to 0.22.0
1a6dcb8
Select commit
Loading
Failed to load commit list.
GitHub Actions / Security audit succeeded Sep 2, 2024 in 0s

Security advisories found

1 unsound

Details

Warnings

RUSTSEC-2023-0055

Multiple soundness issues

Details
Status unsound
Package lexical
Version 6.1.1
Date 2023-09-03

lexical contains multiple soundness issues:

  1. Bytes::read() allows creating instances of types with invalid bit patterns
  2. BytesIter::read() advances iterators out of bounds
  3. The BytesIter trait has safety invariants but is public and not marked unsafe
  4. write_float() calls MaybeUninit::assume_init() on uninitialized data, which is is not allowed by the Rust abstract machine

The crate also has some correctness issues and appears to be unmaintained.

Alternatives

For quickly parsing floating-point numbers third-party crates are no longer needed. A fast float parsing algorithm by the author of lexical has been merged into libcore.

For quickly parsing integers, consider atoi and btoi crates (100% safe code). atoi_radix10 provides even faster parsing, but only with -C target-cpu=native, and at the cost of some unsafe.

For formatting integers in a #[no_std] context consider the numtoa crate.

For working with big numbers consider num-bigint and num-traits.