rustsec-2018-0020
Vulnerability from osv_rustsec
Affected versions contained a possible use-after-free issue with property list iteration
due to a lack of a lifetime constraint tying the lifetime of a proplist::Iterator to the
Proplist object for which it was created. This made it possible for users, without
experiencing a compiler error/warning, to destroy the Proplist object before the iterator,
thus destroying the underlying C object the iterator works upon, before the iterator may be
finished with it.
This impacts all versions of the crate before 2.5.0 back to 1.0.5. Before version
1.0.5 the function that produces the iterator was broken to the point of being useless.
| URL | Type | |
|---|---|---|
{
"affected": [
{
"database_specific": {
"categories": [
"memory-corruption"
],
"cvss": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N",
"informational": null
},
"ecosystem_specific": {
"affected_functions": null,
"affects": {
"arch": [],
"functions": [],
"os": []
}
},
"package": {
"ecosystem": "crates.io",
"name": "libpulse-binding",
"purl": "pkg:cargo/libpulse-binding"
},
"ranges": [
{
"events": [
{
"introduced": "1.0.5"
},
{
"fixed": "2.5.0"
}
],
"type": "SEMVER"
}
],
"versions": []
}
],
"aliases": [
"CVE-2018-25001",
"GHSA-6gvc-4jvj-pwq4",
"GHSA-f56g-chqp-22m9"
],
"database_specific": {
"license": "CC0-1.0"
},
"details": "Affected versions contained a possible use-after-free issue with property list iteration\ndue to a lack of a lifetime constraint tying the lifetime of a `proplist::Iterator` to the\n`Proplist` object for which it was created. This made it possible for users, without\nexperiencing a compiler error/warning, to destroy the `Proplist` object before the iterator,\nthus destroying the underlying C object the iterator works upon, before the iterator may be\nfinished with it.\n\nThis impacts all versions of the crate before `2.5.0` back to `1.0.5`. Before version\n`1.0.5` the function that produces the iterator was broken to the point of being useless.",
"id": "RUSTSEC-2018-0020",
"modified": "2024-02-10T15:57:43Z",
"published": "2018-12-22T12:00:00Z",
"references": [
{
"type": "PACKAGE",
"url": "https://crates.io/crates/libpulse-binding"
},
{
"type": "ADVISORY",
"url": "https://rustsec.org/advisories/RUSTSEC-2018-0020.html"
},
{
"type": "ADVISORY",
"url": "https://github.com/advisories/GHSA-6gvc-4jvj-pwq4"
}
],
"related": [],
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N",
"type": "CVSS_V3"
}
],
"summary": "Possible use-after-free with `proplist::Iterator`"
}
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.
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.