rustsec-2022-0074
Vulnerability from osv_rustsec
Published
2022-12-02 12:00
Modified
2023-06-13 13:10
Summary
Force cast a &Vec<T> to &[T]
Details
In function Table::as_ref, a reference of vector is force cast to slice. There are multiple problems here:
1. To guarantee the size is correct, we have to first do Vec::shrink_to_fit. The function requires a mutable reference, so we have to force cast from immutable to mutable, which is UB.
2. Even if (1) is sound, &Vec<T> and &[T] still might not have the same layout. Treating them equally may lead to UB.
{
"affected": [
{
"database_specific": {
"categories": [],
"cvss": null,
"informational": "unsound"
},
"ecosystem_specific": {
"affected_functions": null,
"affects": {
"arch": [],
"functions": [],
"os": []
}
},
"package": {
"ecosystem": "crates.io",
"name": "prettytable-rs",
"purl": "pkg:cargo/prettytable-rs"
},
"ranges": [
{
"events": [
{
"introduced": "0.0.0-0"
},
{
"fixed": "0.10.0"
}
],
"type": "SEMVER"
}
],
"versions": []
}
],
"aliases": [
"GHSA-gfgm-chr3-x6px"
],
"database_specific": {
"license": "CC0-1.0"
},
"details": "In function `Table::as_ref`, a reference of vector is force cast to slice. There are multiple problems here:\n1. To guarantee the size is correct, we have to first do `Vec::shrink_to_fit`. The function requires a mutable reference, so we have to force cast from immutable to mutable, which is UB.\n2. Even if (1) is sound, `\u0026Vec\u003cT\u003e` and `\u0026[T]` still might not have the same layout. Treating them equally may lead to UB.",
"id": "RUSTSEC-2022-0074",
"modified": "2023-06-13T13:10:24Z",
"published": "2022-12-02T12:00:00Z",
"references": [
{
"type": "PACKAGE",
"url": "https://crates.io/crates/prettytable-rs"
},
{
"type": "ADVISORY",
"url": "https://rustsec.org/advisories/RUSTSEC-2022-0074.html"
},
{
"type": "REPORT",
"url": "https://github.com/phsym/prettytable-rs/issues/145"
}
],
"related": [],
"severity": [],
"summary": "Force cast a \u0026Vec\u003cT\u003e to \u0026[T]"
}
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…