# CVE-2020-35923: ordered_float:NotNan may contain NaN after panic in assignment operators

> The ordered-float crate allows NotNan values to contain NaN, violating type invariants and potentially causing logic errors in dependent applications.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 31 Dec 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-566x-hhrf-qf8m, RUSTSEC-2020-0082

## What is CVE-2020-35923?

CVE-2020-35923 is a medium-severity vulnerability in n/a, published on 31 Dec 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-416 (Use After Free)

## Which versions are affected by CVE-2020-35923?

5 open source packages ship an affected version, including ordered-float. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ordered-float` | crates.io | From 0.2.2 | 1.1.1, 2.0.1 |
| `ordered-float` | crates.io | From 0.2.2 | 1.1.1 |
| `ordered-float` | crates.io | From 0.2.2 | 1.1.1 |
| `ordered-float` | crates.io | From 2.0.0 | 2.0.1 |
| `ordered-float` | crates.io | From 2.0.0 | 2.0.1 |

Products: Ordered-Float Project Ordered-Float.

## How do I fix CVE-2020-35923?

Upgrade ordered-float to a fixed version for your release line: 1.1.1 or 2.0.1.

## Is CVE-2020-35923 being exploited?

There is no known exploitation of CVE-2020-35923 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-35923 and fix it if it is affected.

What it is: CVE-2020-35923 is a medium-severity vulnerability in n/a, published on 31 Dec 2020. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-35923 in the wild and no public exploit code.

Affected packages and fixed versions:
- ordered-float (crates.io): affected from 0.2.2; fixed in 1.1.1, 2.0.1
- ordered-float (crates.io): affected from 0.2.2; fixed in 1.1.1
- ordered-float (crates.io): affected from 0.2.2; fixed in 1.1.1
- ordered-float (crates.io): affected from 2.0.0; fixed in 2.0.1
- ordered-float (crates.io): affected from 2.0.0; fixed in 2.0.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-35923/ (Markdown: https://insights.sbomify.com/CVE-2020-35923/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-35923
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-35923
- OSV: https://osv.dev/vulnerability/CVE-2020-35923

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-35923/
Summaries are generated and may contain mistakes; the official description above is the record.