# RUSTSEC-2023-0028: buf_redux is Unmaintained

> The buf_redux Rust crate is unmaintained and archived, posing supply chain risks due to lack of security updates and potential unsafe code issues.

- **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:** 24 Jan 2023

## What is RUSTSEC-2023-0028?

RUSTSEC-2023-0028 is a vulnerability in buf_redux, published on 24 Jan 2023. 

### Official description

Last release was over three years ago.

The maintainer(s) have been unreachable to respond to any issues that may or may not include security issues.

The repository is now archived and there is no security policy in place to contact the maintainer(s) otherwise.

The safety-undocumented unsafe in the crate may or may not be safe to use.

The crate also has a current future incompatibility warning [buf_redux/23](https://github.com/abonander/buf_redux/issues/23).

## Possible Alternatives

The below may or may not provide alternative(s)

- Rust alloc / std vec::Vec, collections::VecDeque
- [buffer-redux](https://crates.io/crates/buffer-redux) - fork
- [bytes](https://crates.io/crates/bytes)
- [crates.io search for 'buffer'](https://crates.io/keywords/buffer)

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

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


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

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

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

## Is RUSTSEC-2023-0028 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: RUSTSEC-2023-0028 is a vulnerability in buf_redux, published on 24 Jan 2023. 
Exploitation: There is no known exploitation of RUSTSEC-2023-0028 in the wild and no public exploit code.

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

## Sources

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

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