Advisory

RUSTSEC-2022-0063

Also known as: CVE-2022-36086, GHSA-xg8p-34w2-j49j

Summary

Multiple vulnerabilities resulting in out-of-bounds writes

Details

  • The heap initialization methods were missing a minimum size check for the given heap size argument. This could lead to out-of-bound writes when a heap was initialized with a size smaller than 3 * size_of::<usize> because of metadata write operations.
  • When calling Heap::extend with a size smaller than two usizes (e.g., 16 on x86_64), the size was erroneously rounded up to the minimum size, which could result in an out-of-bounds write.
  • Calling Heap::extend on an empty heap tried to construct a heap starting at address 0, which is also an out-of-bounds write.
  • One specific way to trigger this accidentally is to call Heap::new (or a similar constructor) with a heap size that is smaller than two usizes. This was treated as an empty heap as well.
  • Calling Heap::extend on a heap whose size is not a multiple of the size of two usizes resulted in unaligned writes. It also left the heap in an unexpected state, which might lead to subsequent issues. We did not find a way to exploit this undefined behavior yet (apart from DoS on platforms that fault on unaligned writes).

Severity

High Basis: CVSS v3 score 8.4, vector CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Dates

Published
2022-09-07 12:00 UTC
Modified
2026-10-12 18:00 UTC

Affected packages and fixes

linked_list_allocator

crates.io · All systems

Affected

  • introduced 0.0.0-0, fixed 0.10.2 (semver)

Fixed versions

0.10.2

Fix

  • Fixed version 0.10.2
    cargo update -p linked_list_allocator --precise 0.10.2

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: RustSec Advisory Database · CC0-1.0

Sources & licences