Skip to content
OpenAdvisories
High · 7.5 GHSA-xfhw-6mc4-mgxf RUSTSEC-2024-0018

crayon: ObjectPool creates uninitialized memory when freeing objects

Published Apr 5, 2024 · Updated Apr 11, 2024 · Assigned by GHSA

Description

As of version 0.6.0, the ObjectPool explicitly creates an uninitialized instance of its type parameter when it attempts to free an object, and swaps it into the storage. This causes instant undefined behavior due to reading the uninitialized memory in order to write it to the pool storage.

Extremely basic usage of the crate can trigger this issue, e.g. this code from a doctest:

```rust
use crayon::prelude::*;
application::oneshot().unwrap();

let mut params = MeshParams::default();

let mesh = video::create_mesh(params, None).unwrap();

// Deletes the mesh object.
video::delete_mesh(mesh); // <-- UB
```

The Clippy warning for this code was silenced in commit c2fde19caf6149d91faa504263f0bc5cafc35de5.

Discovered via https://asan.saethlin.dev/ub?crate=crayon&version=0.7.1

Affected packages

EcosystemPackageAffectedFixedRecord
crates.io crayon >= 0.6.0, <= 0.7.1 — GHSA-xfhw-6mc4-mgxf
crates.io crayon >= 0.6.0 — RUSTSEC-2024-0018

References