Headline
GHSA-c2hm-mjxv-89r4: Multiple soundness issues in lexical
lexical
contains multiple soundness issues:
- Bytes::read() allows creating instances of types with invalid bit patterns
- BytesIter::read() advances iterators out of bounds
- The
BytesIter
trait has safety invariants but is public and not markedunsafe
write_float()
callsMaybeUninit::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 algorith 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
.
- GitHub Advisory Database
- GitHub Reviewed
- GHSA-c2hm-mjxv-89r4
Multiple soundness issues in lexical
Moderate severity GitHub Reviewed Published Sep 4, 2023 to the GitHub Advisory Database
Vulnerability details Dependabot alerts 0
Package
cargo lexical (Rust)
Affected versions
<= 6.1.1
Patched versions
None
Description
lexical contains multiple soundness issues:
- Bytes::read() allows creating instances of types with invalid bit patterns
- BytesIter::read() advances iterators out of bounds
- The BytesIter trait has safety invariants but is public and not marked unsafe
- 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 algorith 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.
References
- https://github.com/Alexhuszagh/rust-lexical
- https://rustsec.org/advisories/RUSTSEC-2023-0055.html
Published to the GitHub Advisory Database
Sep 4, 2023
Reviewed
Sep 4, 2023
Severity
Moderate
Weaknesses
No CWEs
CVE ID
No known CVE
GHSA ID
GHSA-c2hm-mjxv-89r4
Source code
Alexhuszagh/rust-lexical
Checking history
See something to contribute? Suggest improvements for this vulnerability.