5.9 Medium
CVSS3
Attack Vector
NETWORK
Attack Complexity
HIGH
Privileges Required
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality Impact
NONE
Integrity Impact
NONE
Availability Impact
HIGH
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
0.0004 Low
EPSS
Percentile
15.7%
When storing unbounded types in a BTreeMap, a node is represented as a linked list of โmemory chunksโ. It was discovered recently that when we deallocate a node, in some cases only the first memory chunk is deallocated, and the rest of the memory chunks remain (incorrectly) allocated, causing a memory leak. In the worst case, depending on how a canister uses the BTreeMap, an adversary could interact with the canister through its API and trigger interactions with the map that keep consuming memory due to the memory leak. This could potentially lead to using an excessive amount of memory, or even running out of memory.
This issue has been fixed in #212 https://github.com/dfinity/stable-structures/pull/212 ย by changing the logic for deallocating nodes to ensure that all of a nodeโs memory chunks are deallocated and users are asked to upgrade to version 0.6.4โฆ Tests have been added to prevent regressions of this nature moving forward. Note:ย Users of stable-structure < 0.6.0 are not affected.
Users who are not storing unbounded types in BTreeMapย are not affected and do not need to upgrade. Otherwise, an upgrade to version 0.6.4ย is necessary.
[
{
"collectionURL": "https://crates.io/crates/ic-stable-structures",
"defaultStatus": "unaffected",
"packageName": "ic-stable-structures",
"product": "ic-stable-structures",
"repo": "https://github.com/dfinity/stable-structures",
"vendor": "Internet Computer",
"versions": [
{
"lessThan": "0.6.4",
"status": "affected",
"version": "0.6.0",
"versionType": "semver"
}
]
}
]