Advisory

GHSA-566x-hhrf-qf8m

Also known as: CVE-2020-35923, RUSTSEC-2020-0082

Summary

ordered_float:NotNan may contain NaN after panic in assignment operators

Details

After using an assignment operators such as NotNan::add_assign, NotNan::mul_assign, etc., it was possible for the resulting NotNan value to contain a NaN. This could cause undefined behavior in safe code, because the safe NotNan::cmp method contains internal unsafe code that assumes the value is never NaN. (It could also cause undefined behavior in third-party unsafe code that makes the same assumption, as well as logic errors in safe code.)

This was mitigated starting in version 0.4.0, by panicking if the assigned value is NaN. However, in affected versions from 0.4.0 onward, code that uses the NotNan value during unwinding, or that continues after catching the panic, could still observe the invalid value and trigger undefined behavior.

The flaw is fully corrected in versions 1.1.1 and 2.0.1, by ensuring that the assignment operators panic without modifying the operand, if the result would be NaN.

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2021-08-25 20:50 UTC
Modified
2023-11-08 04:03 UTC

Affected packages and fixes

ordered-float

crates.io · All systems

Affected

  • introduced 2.0.0, fixed 2.0.1 (semver)

Fixed versions

2.0.1

Fix

  • Fixed version 2.0.1
    cargo update -p ordered-float --precise 2.0.1

ordered-float

crates.io · All systems

Affected

  • introduced 0.2.2, fixed 1.1.1 (semver)

Fixed versions

1.1.1

Fix

  • Fixed version 1.1.1
    cargo update -p ordered-float --precise 1.1.1

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: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences