Rust advisories / scanner
Unsound LowRUSTSEC-2025-0033 · scanner
RUSTSEC-2025-0033: Public API without sufficient bounds checking
Short answerscanner has an API that can cause undefined behaviour from safe code: Public API without sufficient bounds checking. No fixed version yet.
| Crate | scanner |
|---|---|
| Type | Unsound (memory-corruption) |
| Affected versions | Every version. |
| Fixed in | none |
| Severity | Low (GitHub rating) |
| Published | 2025-03-27 |
| Last changed | 2025-10-28 |
| Also known as | GHSA-79m9-55jc-p6mw |
| Affected functions | scanner::Match::get, scanner::Match::ptr |
What to do
- Find who pulls it in:
cargo tree -i scanner. - Avoid the affected API (
scanner::Match::get,scanner::Match::ptr), or replace the crate.
Details from the advisory
Match::get() and Match::ptr() lack sufficient bounds checks, leading to potential out of bounds reads.
References
- Package: crates.io/crates/scanner
- Advisory: rustsec.org/advisories/RUSTSEC-2025-0033.html
- Web: github.com/pombredanne/scanner-rs/pull/1
From the RustSec Advisory Database (CC0-1.0) via the OSV export, downloaded Oct 24, 2026. Severity score computed from the published CVSS vector.
Up next
Are you affected?Check your whole dependency treePaste Cargo.lock: every advisory, for your exact versions.Read it next →Also worth your time
Did this answer your question?