Skip to content
Fencer Intel
high —

GHSA-wwxp-hxh6-8gf8 json

binary_vec_io access memory out-of-bounds in binary_read_to_ref and binary_write_from_ref

published last yr. modified last yr. also RUSTSEC-2025-0109

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

Safe functions accept a single `&T` or `&mut T` but multiply by `n` to create slices extending beyond allocated memory when `n > 1`.

These functions use `from_raw_parts` to create slices larger than the underlying allocation, violating memory safety.

The binary_vec_io repository is archived and unmaintained.

Is GHSA-wwxp-hxh6-8gf8 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 binary_vec_io
<=0.1.12
>=0.0.0-0
 no fix listed

Classification

Weakness
  • CWE-120 Buffer Copy without Checking Size of Input

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.