metacall
Affected
- introduced
0.0.0-0(semver)
Fixed versions
None listed
Fix
No fixed version is listed.
Advisory
Also known as: None
Null-pointer dereference and double-free via safe APIs
Two soundness violations exist in the Rust bindings for MetaCall:
Null-pointer dereference: MetaCallFuture::new_raw() accepts a raw
pointer without validation. The Debug impl calls Box::from_raw(self.data)
on it. Passing a null pointer causes the Debug impl to construct aNonNull from null, producing undefined behavior.
Double-free: MetaCallPointer::clone() shares the same rust_value raw
pointer between the clone and the original. Calling get_value_untyped() on
both clones calls Box::from_raw on the same pointer twice, resulting in a
double-free.
Both issues can be triggered through safe public APIs —MetaCallFuture::new_raw(), MetaCallPointer::new(), clone(), andget_value_untyped() — with no unsafe required from the caller.
Not rated by the source.
0.0.0-0 (semver)None listed
No fixed version is listed.
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
Source: RustSec Advisory Database · CC0-1.0