# RUSTSEC-2024-0394: mmap unmaintained

> The unmaintained mmap crate poses supply chain risks; developers should migrate to the memmap2 crate.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 10 Jun 2024

## What is RUSTSEC-2024-0394?

RUSTSEC-2024-0394 is a vulnerability in mmap, published on 10 Jun 2024. 

### Official description

The `mmap` crate is unmaintained as its [repository has been archived](https://github.com/rbranson/rust-mmap) on Feb 10, 2022.
The main alternative seems to be `memmap2` crate.

## Which versions are affected by RUSTSEC-2024-0394?

1 open source package ship an affected version, including mmap.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mmap` | crates.io | From 0.0.0-0 | None |

## How do I fix RUSTSEC-2024-0394?

No fix has been published for RUSTSEC-2024-0394 yet. Limit exposure of the affected software until one is available.

## Is RUSTSEC-2024-0394 being exploited?

There is no known exploitation of RUSTSEC-2024-0394 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for RUSTSEC-2024-0394 and fix it if it is affected.

What it is: RUSTSEC-2024-0394 is a vulnerability in mmap, published on 10 Jun 2024. 
Exploitation: There is no known exploitation of RUSTSEC-2024-0394 in the wild and no public exploit code.

Affected packages and fixed versions:
- mmap (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/RUSTSEC-2024-0394/ (Markdown: https://insights.sbomify.com/RUSTSEC-2024-0394/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/RUSTSEC-2024-0394

---
From sbomify Insights: https://insights.sbomify.com/RUSTSEC-2024-0394/
Summaries are generated and may contain mistakes; the official description above is the record.