# GHSA-79m9-55jc-p6mw: Public API without sufficient bounds checking

> Attackers can trigger out-of-bounds reads via public API methods, potentially causing crashes or leaking memory contents.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Mar 2025
- **Also known as:** RUSTSEC-2025-0033

## What is GHSA-79m9-55jc-p6mw?

GHSA-79m9-55jc-p6mw is a memory corruption vulnerability in scanner, published on 27 Mar 2025. 

### Official description

`Match::get()` and `Match::ptr()` lack sufficient bounds checks, leading to potential out of bounds reads.

## Which versions are affected by GHSA-79m9-55jc-p6mw?

3 open source packages ship an affected version, including scanner.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `scanner` | crates.io | All versions to 0.1.0 | None |
| `scanner` | crates.io | All versions to 0.1.0 | None |
| `scanner` | crates.io | From 0.0.0-0 | None |

## How do I fix GHSA-79m9-55jc-p6mw?

No fix has been published for GHSA-79m9-55jc-p6mw yet. Limit exposure of the affected software until one is available.

## Is GHSA-79m9-55jc-p6mw being exploited?

There is no known exploitation of GHSA-79m9-55jc-p6mw in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-79m9-55jc-p6mw and fix it if it is affected.

What it is: GHSA-79m9-55jc-p6mw is a memory corruption vulnerability in scanner, published on 27 Mar 2025. 
Exploitation: There is no known exploitation of GHSA-79m9-55jc-p6mw in the wild and no public exploit code.

Affected packages and fixed versions:
- scanner (crates.io): affected all versions up to 0.1.0; no fix listed
- scanner (crates.io): affected all versions up to 0.1.0; no fix listed
- scanner (crates.io): affected from 0.0.0-0; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-79m9-55jc-p6mw/ (Markdown: https://insights.sbomify.com/GHSA-79m9-55jc-p6mw/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-79m9-55jc-p6mw

---
From sbomify Insights: https://insights.sbomify.com/GHSA-79m9-55jc-p6mw/
Summaries are generated and may contain mistakes; the official description above is the record.