GHSA-JCR6-4FRQ-9GJJ
Vulnerability from github – Published: 2023-09-11 20:43 – Updated: 2023-09-13 14:04Affected versions dereference a potentially unaligned pointer. The pointer is commonly unaligned in practice, resulting in undefined behavior.
In some build modes, this is observable as a panic followed by abort. In other build modes the UB may manifest in some other way, including the possibility of working correctly in some architectures.
The crate is not currently maintained, so a patched version is not available.
Recommended alternatives
{
"affected": [
{
"package": {
"ecosystem": "crates.io",
"name": "users"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"last_affected": "0.11.0"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [],
"database_specific": {
"cwe_ids": [],
"github_reviewed": true,
"github_reviewed_at": "2023-09-11T20:43:31Z",
"nvd_published_at": null,
"severity": "MODERATE"
},
"details": "Affected versions dereference a potentially unaligned pointer. The pointer is commonly unaligned in practice, resulting in undefined behavior.\n\nIn some build modes, this is observable as a panic followed by abort. In other build modes the UB may manifest in some other way, including the possibility of working correctly in some architectures.\n\nThe crate is not currently maintained, so a patched version is not available.\n\n## Recommended alternatives\n- [`uzers`](https://crates.io/crates/uzers) (an actively maintained fork of the `users` crate)\n- [`sysinfo`](https://crates.io/crates/sysinfo)\n",
"id": "GHSA-jcr6-4frq-9gjj",
"modified": "2023-09-13T14:04:07Z",
"published": "2023-09-11T20:43:31Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/ogham/rust-users/issues/55"
},
{
"type": "PACKAGE",
"url": "https://github.com/ogham/rust-users"
},
{
"type": "WEB",
"url": "https://rustsec.org/advisories/RUSTSEC-2023-0059.html"
}
],
"schema_version": "1.4.0",
"severity": [],
"summary": "Users vulnerable to unaligned read of `*const *const c_char` pointer"
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
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.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.