GHSA-pr59-jjr4-gcf6 json
anon-vec lacks sufficient checks in public API
published last yr. modified last yr. also RUSTSEC-2025-0039
- 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
The following functions in the anon-vec crate are unsound due to insufficient checks on their arguments::
- `AnonVec::get_ref()` - `AnonVec::get_mut()` - `AnonVec::remove_get()`
The crate was built as a learning project and is not being maintained.
Is GHSA-pr59-jjr4-gcf6 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 | anon-vec | <=0.1.1 >=0.0.0-0 |
no fix listed |
Classification
- Weakness
-
- CWE-20 Improper Input Validation
References
-
github.com
/RylanYancey/anon-vec
web
-
rustsec.org
/advisories/RUSTSEC-2025-0039.html
web, advisory
-
crates.io
/crates/anon-vec
package
Sources
- GitHub Advisory GHSA-pr59-jjr4-gcf6
- OSV RUSTSEC-2025-0039
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.