Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

crates.io package

unsafe-libyaml

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Unratedcrates.ioPublished

    unsafe-libyaml unaligned write of u64 on 32-bit and 16-bit platforms

    GHSA-r24f-hg58-vfrw

    Affected
    • crates.io unsafe-libyaml < 0.2.10
    Fixed in
    0.2.10· Vendor fix available
    Issue
    Affected versions allocate memory using the alignment of usize and write data to it of type u64, without using core::ptr::writeunaligned. 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.

    Recommended action: Upgrade to 0.2.10 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →