rustsec-2020-0037
Vulnerability from osv_rustsec
Published
2020-08-31 12:00
Modified
2023-06-13 13:10
Summary
Misbehaving `HandleLike` implementation can lead to memory safety violation
Details
Unsafe code in ObjectPool has time-of-check to time-of-use (TOCTOU) bug that
can eventually lead to a memory safety violation. ObjectPool and HandlePool
implicitly assumes that HandleLike trait methods are pure, i.e., they always
return the same value. However, this assumption is unsound since HandleLike
is a safe, public trait that allows a custom implementation.
{
"affected": [
{
"database_specific": {
"categories": [],
"cvss": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H",
"informational": "unsound"
},
"ecosystem_specific": {
"affected_functions": null,
"affects": {
"arch": [],
"functions": [],
"os": []
}
},
"package": {
"ecosystem": "crates.io",
"name": "crayon",
"purl": "pkg:cargo/crayon"
},
"ranges": [
{
"events": [
{
"introduced": "0.0.0-0"
}
],
"type": "SEMVER"
}
],
"versions": []
}
],
"aliases": [
"CVE-2020-35889",
"GHSA-m833-jv95-mfjh"
],
"database_specific": {
"license": "CC0-1.0"
},
"details": "Unsafe code in `ObjectPool` has time-of-check to time-of-use (TOCTOU) bug that\ncan eventually lead to a memory safety violation. `ObjectPool` and `HandlePool`\nimplicitly assumes that `HandleLike` trait methods are pure, i.e., they always\nreturn the same value. However, this assumption is unsound since `HandleLike`\nis a safe, public trait that allows a custom implementation.",
"id": "RUSTSEC-2020-0037",
"modified": "2023-06-13T13:10:24Z",
"published": "2020-08-31T12:00:00Z",
"references": [
{
"type": "PACKAGE",
"url": "https://crates.io/crates/crayon"
},
{
"type": "ADVISORY",
"url": "https://rustsec.org/advisories/RUSTSEC-2020-0037.html"
},
{
"type": "REPORT",
"url": "https://github.com/shawnscode/crayon/issues/87"
}
],
"related": [],
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
],
"summary": "Misbehaving `HandleLike` implementation can lead to memory safety violation"
}
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…