Ruspiro SingletonApplication · Ruspiro Singleton Project
CVE-2020-36435
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 ruspiro-singleton crate before 0.4.1 for Rust. In Singleton, Send and Sync do not have bounds checks.
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 · moderate confidenceThe ruspiro-singleton crate before version 0.4.1 has unsafe Send and Sync trait implementations that lack proper bounds checks. This allows types that are not actually thread-safe to be incorrectly marked as Send or Sync, potentially leading to data races and undefined behavior in concurrent Rust code.
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
Ruspiro SingletonApplication
< 0.4.1CVSS 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.
-
Check ruspiro-singleton version in Cargo.lockSearch for 'ruspiro-singleton' in your project's Cargo.lock file and note the version number in the name field (e.g., name = "ruspiro-singleton" version = "x.x.x")Affected if The version listed is lower than 0.4.1 (e.g., 0.4.0, 0.3.x, etc.)
-
Verify dependency in Cargo.tomlInspect your Cargo.toml file's [dependencies] or [dev-dependencies] section for ruspiro-singleton and note the specified version rangeAffected if The version specification allows versions below 0.4.1 (e.g., ">=0.1.0", "0.4.0", or no upper bound like ">=0.4.0")
-
List crate dependencies with versionsRun 'cargo tree -p ruspiro-singleton' or 'cargo list --format json' to query the actual resolved version of ruspiro-singleton in your buildAffected if The displayed version is any version below 0.4.1
-
Check for direct usage of unsafe Send/SyncSearch your codebase for implementations that derive Send or Sync on types containing ruspiro-singleton wrappers, especially with 'unsafe' keywordAffected if Your code implements Send or Sync using ruspiro-singleton types without manual thread-safety verification
You are affected if the ruspiro-singleton crate version in your dependency tree is any version prior to 0.4.1, as those versions contain the unsafe trait implementation flaw.
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.1
Upgrade ruspiro-singleton to version 0.4.1 or later, which contains proper bounds checking on the Send and Sync trait implementations. Review any custom Singleton implementations that may depend on this crate's unsafe traits.
0.4.1
- Update the ruspiro-singleton crate dependency in your Cargo.toml to version 0.4.1 or later
- Run `cargo update` to fetch the updated dependency
- Run `cargo build` to verify the fix compiles successfully
- Run `cargo test` to ensure existing tests pass with the updated crate
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Ruspiro Singleton
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-36435 — 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-36435 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