GHSA-c2hm-mjxv-89r4

Suggest an improvement
Source
https://github.com/advisories/GHSA-c2hm-mjxv-89r4
Import Source
https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2023/09/GHSA-c2hm-mjxv-89r4/GHSA-c2hm-mjxv-89r4.json
JSON Data
https://api.osv.dev/v1/vulns/GHSA-c2hm-mjxv-89r4
Aliases
Published
2023-09-04T17:02:00Z
Modified
2024-09-16T16:50:14Z
Summary
Multiple soundness issues in lexical
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 <code>BytesIter</code> trait has safety invariants but is public and not marked <code>unsafe</code>
  4. <code>write_float()</code> calls <code>MaybeUninit::assume_init()</code> on uninitialized data, which is is not allowed by the Rust abstract machine
    1. <code>radix()</code> calls <code>MaybeUninit::assume_init()</code> 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 <code>numtoa</code> crate.

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

Database specific
{
    "github_reviewed": true,
    "cwe_ids": [],
    "github_reviewed_at": "2023-09-04T17:02:00Z",
    "nvd_published_at": null,
    "severity": "LOW"
}
References

Affected packages

crates.io / lexical

Package

Affected ranges

Type
SEMVER
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
7.0.0

Database specific

{
    "last_known_affected_version_range": "<= 6.1.1"
}