# RUSTSEC-2023-0081: safemem is unmaintained

> The safemem library is unmaintained and archived, requiring developers to migrate to standard Rust library functions to avoid supply chain risks.

- **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:** 14 Feb 2023

## What is RUSTSEC-2023-0081?

RUSTSEC-2023-0081 is a vulnerability in safemem, published on 14 Feb 2023. 

### Official description

The latest crates.io release was in 2019. The repository has been archived by the author.

## Migration

- `safemem::copy_over(slice, src_idx, dest_idx, len);` can be replaced with `slice.copy_within(src_idx..src_idx+len, dest_idx);` as of `rust 1.37.0`.
- `safemem::write_bytes(slice, byte);` can be replaced with `slice.fill(byte);` as of `rust 1.50.0`
- `safemem::prepend(slice, vec);` can be replaced with

  ```rust
  let old_len = vec.len();
  vec.extend_from_slice(slice);
  vec.rotate_left(old_len);
  ```
  
  as of `rust 1.26.0`

## Which versions are affected by RUSTSEC-2023-0081?

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


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

## How do I fix RUSTSEC-2023-0081?

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

## Is RUSTSEC-2023-0081 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for RUSTSEC-2023-0081 and fix it if it is affected.

What it is: RUSTSEC-2023-0081 is a vulnerability in safemem, published on 14 Feb 2023. 
Exploitation: There is no known exploitation of RUSTSEC-2023-0081 in the wild and no public exploit code.

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

## Sources

- OSV: https://osv.dev/vulnerability/RUSTSEC-2023-0081

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