Skip to content

Duplicate Advisory: `#[zeroize(drop)]` doesn't implement `Drop` for `enum`s

High severity GitHub Reviewed Published Jun 17, 2022 to the GitHub Advisory Database • Updated Jan 12, 2023
Withdrawn This advisory was withdrawn on Jun 23, 2022

Package

cargo zeroize_derive (Rust)

Affected versions

< 1.1.1

Patched versions

1.1.1

Description

Duplicate Advisory

This advisory is a duplicate of GHSA-c5hx-w945-j4pq. This link is preserved to maintain external references.

Original Description

Affected versions of this crate did not implement Drop when #[zeroize(drop)] was used on an enum.

This can result in memory not being zeroed out after dropping it, which is exactly what is intended when adding this attribute.

The flaw was corrected in version 1.2 and #[zeroize(drop)] on enums now properly implements Drop.

References

Published to the GitHub Advisory Database Jun 17, 2022
Reviewed Jun 17, 2022
Withdrawn Jun 23, 2022
Last updated Jan 12, 2023

Severity

High

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
None
Availability
None

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:N/A:N

Weaknesses

CVE ID

No known CVE

GHSA ID

GHSA-r45x-ghr2-qjxc

Source code

Credits

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