# CVE-2020-35927: Data races in thex

> The thex Rust crate allows cross-thread data races on non-Send types, potentially leading to memory corruption or undefined behavior.

- **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:** No
- **Published:** 31 Dec 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-j42v-6wpm-r847, RUSTSEC-2020-0090

## What is CVE-2020-35927?

CVE-2020-35927 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 thex crate through 2020-12-08 for Rust. Thex<T> allows cross-thread data races of non-Send types.

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

3 open source packages ship an affected version, including thex. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `thex` | crates.io | All versions to 0.1.0 | None |
| `thex` | crates.io | All versions to 0.1.0 | None |
| `thex` | crates.io | From 0.0.0-0 | None |

Products: Thex Project Thex.

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

No fix has been published for CVE-2020-35927 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-35927 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-35927 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-35927 in the wild and no public exploit code.

Affected packages and fixed versions:
- thex (crates.io): affected all versions up to 0.1.0; no fix listed
- thex (crates.io): affected all versions up to 0.1.0; no fix listed
- thex (crates.io): affected from 0.0.0-0; no fix listed

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-35927/ (Markdown: https://insights.sbomify.com/CVE-2020-35927/index.md)
```

## Sources

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

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