- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
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)
Is RUSTSEC-2023-0028 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerAffected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | buf_redux | >=0.0.0-0 |
no fix listed |
References
Sources
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.