array-init-cursor is unsound when used with types that implement `Drop`
Priority LOW 38CWE-672Published · Updated
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- —
- Confidentiality · integrity · availability
- —
- Fix status
- Fixed
No CVSS vector from any source. Fix status from GitHub.
Summary
The `Drop` implementation will get run twice when using the cursor. This issue does not affect you, if you are using only using the crate with types that are `Copy` such as `u8`. This issue also does not affect you, if you are only depending on it through the crate `planus`.
Why it matters now
Fix Fixed array-init-cursor (crates.io): 0.2.1
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 |
|---|---|---|---|---|---|
| — | array-init-cursor (crates.io) | before 0.2.1 | 0.2.1 | Patch available | GHSA-67r5-rqwv-9p9q |
- array-init-cursor (crates.io) Vendor— Affected before 0.2.1 Fixed in 0.2.1 Patch available GHSA-67r5-rqwv-9p9q
Remediation
- Fix · GHSA-67r5-rqwv-9p9q array-init-cursor (crates.io) Fixed in 0.2.1 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-67r5-rqwv-9p9q
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences