GHSA-82HM-VH7G-HRH9
Vulnerability from github – Published: 2021-08-25 21:01 – Updated: 2021-09-09 17:55Impact
Anyone who uses total_size(..) function to partial read the length of any FixVec will get an incorrect result, due to an incorrect implementation. This has been resolved in the 0.7.2 release.
Workarounds
If you already have the whole FixVec A, you can use A.as_slice().len() to get the total size of the FixVec.
For more information
If you have any questions or comments about this advisory:
{
"affected": [
{
"package": {
"ecosystem": "crates.io",
"name": "molecule"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "0.7.2"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [],
"database_specific": {
"cwe_ids": [],
"github_reviewed": true,
"github_reviewed_at": "2021-08-02T18:10:49Z",
"nvd_published_at": null,
"severity": "MODERATE"
},
"details": "### Impact\n\nAnyone who uses `total_size(..)` function to partial read the length of any `FixVec` will get an incorrect result, due to an incorrect implementation. This has been resolved in the 0.7.2 release.\n\n### Workarounds\n\nIf you already have the whole `FixVec` `A`, you can use `A.as_slice().len()` to get the total size of the `FixVec`.\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n- [Open an issue to ask use directly](https://github.com/nervosnetwork/molecule/issues/new).",
"id": "GHSA-82hm-vh7g-hrh9",
"modified": "2021-09-09T17:55:10Z",
"published": "2021-08-25T21:01:25Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/nervosnetwork/molecule/security/advisories/GHSA-82hm-vh7g-hrh9"
},
{
"type": "WEB",
"url": "https://github.com/nervosnetwork/molecule/pull/49"
},
{
"type": "PACKAGE",
"url": "https://github.com/nervosnetwork/molecule"
},
{
"type": "WEB",
"url": "https://rustsec.org/advisories/RUSTSEC-2021-0103.html"
}
],
"schema_version": "1.4.0",
"severity": [],
"summary": "Partial read is incorrect in molecule"
}
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.