Skip to content

Pointer dereference in nanorand

Critical severity GitHub Reviewed Published Jan 6, 2022 to the GitHub Advisory Database • Updated Jun 13, 2023

Package

cargo nanorand (Rust)

Affected versions

>= 0.5.0, < 0.6.1

Patched versions

0.6.1

Description

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.

References

Published by the National Vulnerability Database Dec 27, 2021
Reviewed Jan 5, 2022
Published to the GitHub Advisory Database Jan 6, 2022
Last updated Jun 13, 2023

Severity

Critical

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS score

0.235%
(62nd percentile)

Weaknesses

No CWEs

CVE ID

CVE-2021-45705

GHSA ID

GHSA-r57r-j98g-587f

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.