rustsec-2022-0054
Vulnerability from osv_rustsec
Published
2022-05-11 12:00
Modified
2023-06-13 13:10
Summary
wee_alloc is Unmaintained
Details
Two of the maintainers have indicated that the crate may not be maintained.
The crate has open issues including memory leaks and may not be suitable for production use.
It may be best to switch to the default Rust standard allocator on wasm32 targets.
Last release seems to have been three years ago.
Possible Alternative(s)
The below list has not been vetted in any way and may or may not contain alternatives;
- Rust standard default allocator on wasm32-target
Honorable Mention(s)
The below may serve to educate on potential future alternatives:
{
"affected": [
{
"database_specific": {
"categories": [],
"cvss": null,
"informational": "unmaintained"
},
"ecosystem_specific": {
"affected_functions": null,
"affects": {
"arch": [],
"functions": [],
"os": []
}
},
"package": {
"ecosystem": "crates.io",
"name": "wee_alloc",
"purl": "pkg:cargo/wee_alloc"
},
"ranges": [
{
"events": [
{
"introduced": "0.0.0-0"
}
],
"type": "SEMVER"
}
],
"versions": []
}
],
"aliases": [
"GHSA-rc23-xxgq-x27g"
],
"database_specific": {
"license": "CC0-1.0"
},
"details": "Two of the maintainers have indicated that the crate may not be maintained.\n\nThe crate has open issues including memory leaks and may not be suitable for production use.\n\nIt may be best to switch to the default Rust standard allocator on wasm32 targets.\n\nLast release seems to have been three years ago.\n\n## Possible Alternative(s)\n\n The below list has not been vetted in any way and may or may not contain alternatives;\n\n - Rust standard [default allocator] on wasm32-target\n\n## Honorable Mention(s)\n\n The below may serve to educate on potential future alternatives:\n\n - [lol_alloc](https://crates.io/crates/lol_alloc)\n\n[default allocator]: https://github.com/alexcrichton/dlmalloc-rs",
"id": "RUSTSEC-2022-0054",
"modified": "2023-06-13T13:10:24Z",
"published": "2022-05-11T12:00:00Z",
"references": [
{
"type": "PACKAGE",
"url": "https://crates.io/crates/wee_alloc"
},
{
"type": "ADVISORY",
"url": "https://rustsec.org/advisories/RUSTSEC-2022-0054.html"
},
{
"type": "REPORT",
"url": "https://github.com/rustwasm/wee_alloc/issues/107"
},
{
"type": "WEB",
"url": "https://www.reddit.com/r/rust/comments/x1cle0/dont_use_wee_alloc_in_production_code_targeting/"
},
{
"type": "REPORT",
"url": "https://github.com/rustwasm/wee_alloc/issues/85"
},
{
"type": "REPORT",
"url": "https://github.com/rustwasm/wee_alloc/issues/106"
}
],
"related": [],
"severity": [],
"summary": "wee_alloc is Unmaintained"
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
Loading…