VDB
Sign up
MEDIUM

GHSA-wfg4-322g-9vqv

memoffset allows reading uninitialized memory

Details

memoffset allows attempt of reading data from address `0` with arbitrary type. This behavior is an undefined behavior because address `0` to `std::mem::size_of<T>` may not have valid bit-pattern with `T`. Old implementation dereferences uninitialized memory obtained from `std::mem::align_of`. Older implementation prior to it allows using uninitialized data obtained from `std::mem::uninitialized` with arbitrary type then compute offset by taking the address of field-projection. This may also result in an undefined behavior for "father" that includes (directly or transitively) type that [does not allow to be uninitialized](https://doc.rust-lang.org/nightly/reference/behavior-considered-undefined.html).

This flaw was corrected by using `std::ptr::addr_of` in <https://github.com/Gilnaa/memoffset/pull/50>.

Are you affected?

Enter the version of the package you're using.

Affected packages

crates.io/memoffset
Introduced in: 0Fixed in: 0.6.2

Upgrade memoffset to 0.6.2 or newer (ecosystem crates.io).

References