GHSA-79m9-55jc-p6mw — scanner
Fix: pombredanne/scanner-rs#1GHSA-79m9-55jc-p6mw is a security vulnerability in scanner. No vendor fix is recorded yet; mitigation options are listed below.
scanner has a Public API without sufficient bounds checking
Real-World Exposure
scannerReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.
Description
Match::get() and Match::ptr() lack sufficient bounds checks, leading to potential out of bounds reads.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🦀crates.io | scanner | all versions | No fix |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for scanner, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of scanner has shipped for GHSA-79m9-55jc-p6mw yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-79m9-55jc-p6mw can be triaged on real exposure rather than presence alone.
Tailored to GHSA-79m9-55jc-p6mw. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-79m9-55jc-p6mw in your dependencies?
O3 Security finds GHSA-79m9-55jc-p6mw across crates.io dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.