rustsec-2020-0034
Vulnerability from osv_rustsec
Published
2020-08-25 12:00
Modified
2023-06-13 13:10
Summary
Multiple security issues including data race, buffer overflow, and uninitialized memory drop
Details
arr crate contains multiple security issues. Specifically,
- It incorrectly implements Sync/Send bounds, which allows to smuggle non-Sync/Send types across the thread boundary.
IndexandIndexMutimplementation does not check the array bound.Array::new_from_template()drops uninitialized memory.
References
| URL | Type | |
|---|---|---|
{
"affected": [
{
"database_specific": {
"categories": [
"memory-corruption",
"thread-safety"
],
"cvss": null,
"informational": null
},
"ecosystem_specific": {
"affected_functions": null,
"affects": {
"arch": [],
"functions": [],
"os": []
}
},
"package": {
"ecosystem": "crates.io",
"name": "arr",
"purl": "pkg:cargo/arr"
},
"ranges": [
{
"events": [
{
"introduced": "0.0.0-0"
}
],
"type": "SEMVER"
}
],
"versions": []
}
],
"aliases": [
"CVE-2020-35886",
"CVE-2020-35887",
"CVE-2020-35888",
"GHSA-36xw-hgfv-jwm7",
"GHSA-c7fw-cr3w-wvfc",
"GHSA-fhvj-7f9p-w788"
],
"database_specific": {
"license": "CC0-1.0"
},
"details": "`arr` crate contains multiple security issues. Specifically,\n\n1. It incorrectly implements Sync/Send bounds, which allows to smuggle non-Sync/Send types across the thread boundary.\n2. `Index` and `IndexMut` implementation does not check the array bound.\n3. `Array::new_from_template()` drops uninitialized memory.",
"id": "RUSTSEC-2020-0034",
"modified": "2023-06-13T13:10:24Z",
"published": "2020-08-25T12:00:00Z",
"references": [
{
"type": "PACKAGE",
"url": "https://crates.io/crates/arr"
},
{
"type": "ADVISORY",
"url": "https://rustsec.org/advisories/RUSTSEC-2020-0034.html"
},
{
"type": "REPORT",
"url": "https://github.com/sjep/array/issues/1"
}
],
"related": [],
"severity": [],
"summary": "Multiple security issues including data race, buffer overflow, and uninitialized memory drop"
}
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…