- Reported
-
- Issued
-
- Package
-
secure-gate
(crates.io)
- Type
-
Vulnerability
- Categories
-
- Keywords
-
#zeroize
#drop
#secrets
- References
-
- Patched
-
- Unaffected
-
Description
In affected versions, the Fixed<T> and Dynamic<T> wrappers (and the
FixedNoClone / DynamicNoClone variants in 0.6.x) did not wipe their contents
when dropped. The types implemented the zeroize::ZeroizeOnDrop marker trait,
which has no methods and does nothing by itself, but had no Drop implementation.
The documentation stated that secrets were zeroized on drop.
A secret held in one of these wrappers stayed in the freed stack or heap memory
after the wrapper went out of scope, where it could be read by anything able to
observe that memory later, such as a core dump, swap, or a separate memory
disclosure bug.
Versions before 0.5.0 are not affected: with the default zeroize feature they
stored the secret in secrecy::SecretBox or zeroize::Zeroizing, both of which
wipe on drop.
The flaw was fixed by making zeroize a required dependency, bounding the
wrappers on T: Zeroize, and adding Drop implementations that call
zeroize(). The first published release with the fix is 0.8.0-rc.1; the first
stable release is 0.8.0. All affected versions have been yanked from crates.io.
Advisory available under CC0-1.0
license.