Advisory

RUSTSEC-2023-0055

Also known as: GHSA-c2hm-mjxv-89r4

Summary

Multiple soundness issues

Details

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
  5. `radix()` calls `MaybeUninit::assume_init()` on uninitialized data, which is is not allowed by the Rust abstract machine

The crate also has some correctness issues.

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.

Severity

Not rated by the source.

Dates

Published
2023-09-03 12:00 UTC
Modified
2026-02-04 02:37 UTC

Affected packages and fixes

lexical

crates.io · All systems

Affected

  • introduced 0.0.0-0, fixed 7.0.0 (semver)

Fixed versions

7.0.0

Fix

  • Fixed version 7.0.0
    cargo update -p lexical --precise 7.0.0

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: RustSec Advisory Database · CC0-1.0

Sources & licences