CVE-2020-35923 json
ordered_float:NotNan may contain NaN after panic in assignment operators
published 2020-12-06 5 y ago modified 2026-06-17 4 mo ago also GHSA-566x-hhrf-qf8m , RUSTSEC-2020-0082 , EUVD-2021-1571
- cvss
- 5.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 33%
- public exploits
- 0
- none known
Summary
An issue was discovered in the ordered-float crate before 1.1.1 and 2.x before 2.0.1 for Rust. A NotNan value can contain a NaN.
Patch / fix
- crates.io ordered-float 1.1.1, 2.0.1
- ordered-float_project ordered-float 1.1.1, 2.0.1
Exploit prediction
0.39% chance of exploitation in the next 30 days, higher than 33% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- rustsec.org https://rustsec.org/advisories/RUSTSEC-2020-0082.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
| NVD | 2.0 | 4.9 | AV:L/AC:L/Au:N/C:N/I:N/A:C |
| GitHub | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
| OSV | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | ordered-float | >=2.0.0, <2.0.1 >=0.2.2, <1.1.1 >=2.0.0-0, <2.0.1 |
2.0.1 1.1.1 |
Classification
References
-
github.com
/reem/rust-ordered-float/pull/71
web
-
github.com
/reem/rust-ordered-float/commit/c55cda301c943270b7eb2b4765bedbcce56edb90
web
-
github.com
/reem/rust-ordered-float/commit/da4a8dd49300740a434c095a9c4b408d2415cc08
web
-
rustsec.org
/advisories/RUSTSEC-2020-0082.html
web, exploit, third-party-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2020-35923
advisory
-
github.com
/reem/rust-ordered-float
package
-
crates.io
/crates/ordered-float
package
Sources
- CVE List CVE-2020-35923
- GitHub Advisory GHSA-566x-hhrf-qf8m
- NVD CVE-2020-35923
- OSV RUSTSEC-2020-0082
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.