`Bitmap::try_from(&[u8])` can create invalid values
Exploitation and risk
Source statusCISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.
Which CVEs have scores here?
This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.
No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.
osv · RUSTSEC-2025-0167
PublishedThe `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.
- Source published
- 25 Dec 2025 12:00:00 UTC
- Source modified
- 10 Aug 2026 19:45:04 UTC
- Saved here
- 24 Oct 2026 13:19:54 UTC
- Source terms
- OSV · upstream source license applies
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.