CVE-2020-36440 json
Data races in libsbc
published 5y ago modified 4mo ago also GHSA-f6g6-54hm-fhxv , RUSTSEC-2020-0120 , EUVD-2021-1693
- 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 libsbc crate before 0.1.5 for Rust. For Decoder<R>, it implements Send for any R: Read.
Patch / fix
Is CVE-2020-36440 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
0.77% chance of exploitation in the next 30 days, higher than 55% of all scored CVEs (FIRST EPSS, 2026-11-09).
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 | libsbc | <0.1.5 >=0.0.0-0, <0.1.5 |
0.1.5 |
Classification
References
-
github.com
/mvertescher/libsbc-rs/commit/a34d6e1
web
-
rustsec.org
/advisories/RUSTSEC-2020-0120.html
web, third-party-advisory, advisory
-
raw.githubusercontent.com
/rustsec/advisory-db/main/crates/libsbc/RUSTSEC-2020-0120.md
web, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2020-36440
advisory
-
github.com
/mvertescher/libsbc-rs
package
-
crates.io
/crates/libsbc
package
-
github.com
/mvertescher/libsbc-rs/issues/4
report
Sources
- CVE List CVE-2020-36440
- GitHub Advisory GHSA-f6g6-54hm-fhxv
- NVD CVE-2020-36440
- OSV RUSTSEC-2020-0120
Fencer Intel 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.