CVE-2020-36435 json
Data race in ruspiro-singleton
published 2020-11-16 5 y ago modified 2026-06-17 4 mo ago also GHSA-fqq2-xp7m-xvm8 , RUSTSEC-2020-0115 , EUVD-2021-1707
- cvss
- 8.1
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.8%
- EPSS 0.8% chance of exploitation in 30 days, percentile 55%
- public exploits
- 0
- none known
Summary
An issue was discovered in the ruspiro-singleton crate before 0.4.1 for Rust. In Singleton, Send and Sync do not have bounds checks.
Patch / fix
- crates.io ruspiro-singleton 0.4.1
- ruspiro-singleton_project ruspiro-singleton 0.4.1
- github.com/RusPiRo/ruspiro-singleton@b0d2bd2 commit
- github.com/RusPiRo/ruspiro-singleton#11 pull request
Exploit prediction
0.77% chance of exploitation in the next 30 days, higher than 55% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
| GitHub | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
| OSV | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | ruspiro-singleton | <0.4.1 >=0.0.0-0, <0.4.1 |
0.4.1 |
Classification
References
-
github.com
/RusPiRo/ruspiro-singleton/pull/11
web
-
github.com
/RusPiRo/ruspiro-singleton/commit/b0d2bd20eb40b9cbc2958b981ba2dcd9e6f9396e
web
-
rustsec.org
/advisories/RUSTSEC-2020-0115.html
web, third-party-advisory, advisory
-
raw.githubusercontent.com
/rustsec/advisory-db/main/crates/ruspiro-singleton/RUSTSEC-2020-0115.md
web, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2020-36435
advisory
-
github.com
/RusPiRo/ruspiro-singleton/issues/10
web, report
-
github.com
/RusPiRo/ruspiro-singleton
package
-
crates.io
/crates/ruspiro-singleton
package
Sources
- CVE List CVE-2020-36435
- GitHub Advisory GHSA-fqq2-xp7m-xvm8
- NVD CVE-2020-36435
- OSV RUSTSEC-2020-0115
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.