Tiny FutureApplication · Tiny Future Project
CVE-2020-36438
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn issue was discovered in the tiny_future crate before 0.4.0 for Rust. Future<T> does not have bounds on its Send and Sync traits.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe tiny_future Rust crate before v0.4.0 defines Future<T> without proper Send and Sync trait bounds. This allows futures containing non-thread-safe data to be incorrectly marked as Send/Sync, potentially enabling data races when such futures are moved between threads.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Tiny FutureApplication
< 0.4.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate tiny_future in your dependency treeSearch your Cargo.lock file for 'tiny_future' and note the version number in the [[package]] section, or run 'cargo tree -p tiny_future' to see the installed versionAffected if version is less than 0.4.0
-
Confirm tiny_future is actually usedSearch your source code for 'use tiny_future' or 'tiny_future::Future' imports to confirm the crate is actively imported and usedAffected if tiny_future::Future is imported and used in your codebase
-
Identify if futures are moved across thread boundariesSearch for patterns where Future types are passed to thread spawns, task schedulers, or .awaited inside spawn_blocking or similar thread-crossing contexts. Look for 'std::thread::spawn', 'tokio::spawn', or other async runtime spawn functions operating on tiny_future::Future valuesAffected if tiny_future::Future instances are moved to different threads via spawn functions or similar mechanisms
You are affected if tiny_future version is below 0.4.0 AND your code moves tiny_future::Future instances between threads, allowing potentially non-Send/Sync data to cause data races.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped0.4.0
Upgrade the tiny_future crate to version 0.4.0 or later which adds appropriate Send and Sync trait bounds to Future<T>.
tiny_future 0.4.0
- Check your current tiny_future version in Cargo.toml
- Update the tiny_future dependency in Cargo.toml to version 0.4.0 or later (e.g., tiny_future = "0.4.0")
- Run cargo update tiny_future to fetch the new version
- Run cargo build to verify the upgrade compiles successfully
- Test your application to ensure the changes do not break existing functionality
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Tiny Future
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-36438 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-36438 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data