Shaman has soundness issues and is unmaintained
Priority LOW 38Published · Updated
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- —
- Confidentiality · integrity · availability
- —
- Fix status
- No fix listed
No CVSS vector from any source. Fix status from GitHub.
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.
Why it matters now
Fix No fix listed No fixed version in the sources yet
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | shaman (crates.io) | up to 0.1.0 | — | No fix listed | GHSA-7vjm-6qgq-3mrq |
- shaman (crates.io) Vendor— Affected up to 0.1.0 Fixed in — No fix listed GHSA-7vjm-6qgq-3mrq
Remediation
No fixed version listed by the sources yet.
Timeline
- 2026-10-03 Threatist record created from GHSA-7vjm-6qgq-3mrq
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences