GHSA-7vjm-6qgq-3mrq json
Shaman has soundness issues and is unmaintained
published last yr. modified last yr. also RUSTSEC-2025-0113
- 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
`shaman::cryptoutil::write_u64v_le` and other functions mentioned above cannot garantee memory safety of get_unchecked later if both length are zero.
`shaman` is unmaintained.
Is GHSA-7vjm-6qgq-3mrq 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 | shaman | <=0.1.0 >=0.0.0-0 |
no fix listed |
References
-
crates.io
/crates/shaman
web, package
-
rustsec.org
/advisories/RUSTSEC-2025-0113.html
web, advisory
Sources
- GitHub Advisory GHSA-7vjm-6qgq-3mrq
- OSV RUSTSEC-2025-0113
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.