CVE-2020-36458 json
Data races in lexer
published 5y ago modified 4mo ago also GHSA-f997-8gxg-r354 , RUSTSEC-2020-0138 , EUVD-2021-1696
- 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 57%
- public exploits
- 0
- none known
Summary
An issue was discovered in the lexer crate through 2020-11-10 for Rust. For ReaderResult<T, E>, there is an implementation of Sync with a trait bound of T: Send, E: Send.
Patch / fix
Is CVE-2020-36458 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.83% chance of exploitation in the next 30 days, higher than 57% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- rustsec.org https://rustsec.org/advisories/RUSTSEC-2020-0138.html referenced PoC, tagged "exploit" by a source, unverified
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 |
| OSV | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
| GitHub | 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 | lexer | <=0.1.16 >=0.0.0-0 |
no fix listed |
Classification
References
-
rustsec.org
/advisories/RUSTSEC-2020-0138.html
web, exploit, issue-tracking, patch, third-party-advisory, advisory
-
raw.githubusercontent.com
/rustsec/advisory-db/main/crates/lexer/RUSTSEC-2020-0138.md
web, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2020-36458
advisory
-
gitlab.com
/nathanfaucett/rs-lexer
package
-
gitlab.com
/nathanfaucett/rs-lexer/-/issues/2
web, report
-
crates.io
/crates/lexer
package
Sources
- CVE List CVE-2020-36458
- GitHub Advisory GHSA-f997-8gxg-r354
- NVD CVE-2020-36458
- OSV RUSTSEC-2020-0138
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.