Skip to content
Fencer Intel
no cvss —

RUSTSEC-2024-0448 json

`parse_arguments` reads a caller-supplied pointer as a slice

published last yr. modified last mo.

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

`parse_arguments` is safe. It takes `arguments: *const AnyObject` and `argc`, and calls `slice::from_raw_parts(arguments, argc as usize)`.

It does not check that `arguments` is non-null and aligned, or that `argc` elements are initialized. Safe Rust can pass a null pointer or a length past the allocation. The maintainer confirmed this on 2026-10-03, including a debug abort on Rust 1.78+ when Ruby calls an arity -1 method (`to_s` via `format`, `puts`, or `Array#join`) with a NULL `argv` and `argc` of 0.

Patch / fix

  • crates.io rutie 0.10.3, 0.11.3, 0.12.1, 0.13.1, 0.14.1

Is RUSTSEC-2024-0448 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem package affected fixed in
crates.io rutie
>=0.0.0-0, <0.10.3
>=0.11.0, <0.11.3
>=0.12.0, <0.12.1
>=0.13.0, <0.13.1
>=0.14.0, <0.14.1
0.10.3
0.11.3
0.12.1
0.13.1
0.14.1

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.