The owned-alloc crate has had no release since 2018, and the maintainer has not responded to the upstream issue or to direct contact.
Product
crates.io owned-alloc vulnerabilities
2 published CVES affecting crates.io owned-alloc, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 2
- Critical
- 0
- High
- 0
- Medium
- 0
- Low
- 0
- Unscored
- 2
- CISA KEV
- 0
Latest crates.io owned-alloc CVEs
Newest publication first
-
Unknown
-
Unknown
OwnedAlloc::drop_in_place destroys the contained value by hand, then commits the ownership transfer with mem::forget(self) — which lives inside into_raw and so runs only after the destruction. T::drop is user code and may panic. If it does, the forget is skipped and the still-liv...
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.