Skip to content
Fencer Intel
no cvss —

RUSTSEC-2025-0167 json

`Bitmap::try_from(&[u8])` can create invalid values

published 10mo ago modified 3mo ago

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

The `TryFrom<&[u8]>` implementation for `Bitmap<SIZE>` copies the input bytes into an uninitialized backing store and calls `assume_init()` without validating that the bytes form a valid value of the backing store type. For `SIZE = 1` the backing store is a `bool`, so any input byte other than `0x00` or `0x01` produces an invalid value, which is immediate undefined behavior.

The `AsMut<[u8]>` implementation has the same problem, as it allows safe code to write invalid bit patterns into the backing store through the returned slice.

No fixed version is available, as the crate is unmaintained; its GitHub repository was archived by the owner on 2026-05-03.

Is RUSTSEC-2025-0167 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 bitmaps
>=3.2.0
 no fix listed

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.