CVE-2021-45705 json
Pointer dereference in nanorand
published 5y ago modified 4mo ago also GHSA-p6gj-gpc8-f8xw , GHSA-r57r-j98g-587f , RUSTSEC-2021-0114 , EUVD-2022-0681
- cvss
- 9.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.2%
- EPSS 1.2% chance of exploitation in 30 days, percentile 69%
- public exploits
- 0
- none known
Summary
An issue was discovered in the nanorand crate before 0.6.1 for Rust. There can be multiple mutable references to the same object because the TlsWyRand Deref implementation dereferences a raw pointer.
Patch / fix
- crates.io nanorand 0.6.1
- nanorand_project nanorand 0.6.1
Is CVE-2021-45705 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
1.23% chance of exploitation in the next 30 days, higher than 69% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
| GitHub | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | nanorand | >=0.5.0, <0.6.1 |
0.6.1 |
References
-
rustsec.org
/advisories/RUSTSEC-2021-0114.html
web, third-party-advisory, advisory
-
raw.githubusercontent.com
/rustsec/advisory-db/main/crates/nanorand/RUSTSEC-2021-0114.md
web, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2021-45705
advisory
-
github.com
/Absolucy/nanorand-rs/issues/28
web, report
-
github.com
/Absolucy/nanorand-rs
package
-
crates.io
/crates/nanorand
package
Sources
- CVE List CVE-2021-45705
- GitHub Advisory GHSA-r57r-j98g-587f
- GitHub Advisory GHSA-p6gj-gpc8-f8xw
- NVD CVE-2021-45705
- OSV RUSTSEC-2021-0114
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.