GHSA-79m9-55jc-p6mw json
scanner has a Public API without sufficient bounds checking
published last yr. modified last yr. also RUSTSEC-2025-0033
- 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
`Match::get()` and `Match::ptr()` lack sufficient bounds checks, leading to potential out of bounds reads.
Patch / fix
- github.com/pombredanne/scanner-rs#1 pull request
Is GHSA-79m9-55jc-p6mw 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 FencerAffected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | scanner | <=0.1.0 >=0.0.0-0 |
no fix listed |
Classification
- Weakness
-
- CWE-125 Out-of-bounds Read
References
-
github.com
/pombredanne/scanner-rs/pull/1
web
-
github.com
/pombredanne/scanner-rs
package
-
rustsec.org
/advisories/RUSTSEC-2025-0033.html
web, advisory
-
crates.io
/crates/scanner
package
Sources
- GitHub Advisory GHSA-79m9-55jc-p6mw
- OSV RUSTSEC-2025-0033
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.