GHSA-r24f-hg58-vfrw
unsafe-libyaml unaligned write of u64 on 32-bit and 16-bit platforms
GHSA-r24f-hg58-vfrw is a vulnerability with no CVSS score yet in unsafe-libyaml, published December 20, 2023. No source lists public exploit code. Fixed in unsafe-libyaml 0.2.10.
- Severity
- UnratedNo CVSS score yet
- Exploit chance
- UnscoredNo EPSS score yet
- Exploitation
- None knownNot on CISA’s or ENISA’s lists
- Fixed in
0.2.10unsafe-libyaml +1 more
Description
Affected versions allocate memory using the alignment of usize and write data to it of type u64, without using core::ptr::write_unaligned. In platforms with sub-64bit alignment for usize (including wasm32 and x86) these writes are insufficiently aligned some of the time.
If using an ordinary optimized standard library, the bug exhibits Undefined Behavior so may or may not behave in any sensible way, depending on optimization settings and hardware and other things. If using a Rust standard library built with debug assertions enabled, the bug manifests deterministically in a crash (non-unwinding panic) saying "ptr::write requires that the pointer argument is aligned and non-null".
No 64-bit platform is impacted by the bug.
The flaw was corrected by allocating with adequately high alignment on all platforms.
Affected packages
| Package | Affected | Fixed |
|---|---|---|
unsafe-libyamlcrates.io | before 0.2.10 | 0.2.10 |
unsafe-libyamlcrates.io | 0.0.0-0 up to 0.2.10 | 0.2.10 |
What each source reports
GitHub AdvisoriesNo score
unsafe-libyaml unaligned write of u64 on 32-bit and 16-bit platforms
Affected versions allocate memory using the alignment of usize and write data to it of type u64, without using core::ptr::write_unaligned. In platforms with sub-64bit alignment for usize (including wasm32 and x86) these writes are insufficiently aligned some of the time.
If using an ordinary optimized standard library, the bug exhibits Undefined Behavior so may or may not behave in any sensible way, depending on optimization settings and hardware and other things. If using a Rust standard library built with debug assertions enabled, the bug manifests deterministically in a crash (non-unwinding panic) saying "ptr::write requires that the pointer argument is aligned and non-null".
No 64-bit platform is impacted by the bug.
The flaw was corrected by allocating with adequately high alignment on all platforms.
- Record
GHSA-r24f-hg58-vfrw- Updated
- 2026-11-02
OSVNo score
unsafe-libyaml unaligned write of u64 on 32-bit and 16-bit platforms
Affected versions allocate memory using the alignment of usize and write data to it of type u64, without using core::ptr::write_unaligned. In platforms with sub-64bit alignment for usize (including wasm32 and x86) these writes are insufficiently aligned some of the time.
If using an ordinary optimized standard library, the bug exhibits Undefined Behavior so may or may not behave in any sensible way, depending on optimization settings and hardware and other things. If using a Rust standard library built with debug assertions enabled, the bug manifests deterministically in a crash (non-unwinding panic) saying "ptr::write requires that the pointer argument is aligned and non-null".
No 64-bit platform is impacted by the bug.
The flaw was corrected by allocating with adequately high alignment on all platforms.
- Record
GHSA-r24f-hg58-vfrw- Updated
- 2026-11-02
OSVRUSTSEC-2023-0075No score
Unaligned write of u64 on 32-bit and 16-bit platforms
Affected versions allocate memory using the alignment of usize and write data
to it of type u64, without using core::ptr::write_unaligned. In platforms
with sub-64bit alignment for usize (including wasm32 and x86) these writes
are insufficiently aligned some of the time.
If using an ordinary optimized standard library, the bug exhibits Undefined Behavior so may or may not behave in any sensible way, depending on optimization settings and hardware and other things. If using a Rust standard library built with debug assertions enabled, the bug manifests deterministically in a crash (non-unwinding panic) saying "ptr::write requires that the pointer argument is aligned and non-null".
No 64-bit platform is impacted by the bug.
The flaw was corrected by allocating with adequately high alignment on all platforms.
- Record
RUSTSEC-2023-0075- Updated
- 2026-11-02
History
| Recorded | Changed | Sources |
|---|---|---|
| first indexed | GitHub Advisories, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.