cve-2024-7884
Vulnerability from cvelistv5
Published
2024-09-05 13:01
Modified
2024-09-05 14:42
Severity ?
EPSS score ?
Summary
When a canister method is called via ic_cdk::call* , a new Future CallFuture is created and can be awaited by the caller to get the execution result. Internally, the state of the Future is tracked and stored in a struct called CallFutureState. A bug in the polling implementation of the CallFuture allows multiple references to be held for this internal state and not all references were dropped before the Future is resolved. Since we have unaccounted references held, a copy of the internal state ended up being persisted in the canister's heap and thus causing a memory leak.
Impact Canisters built in Rust with ic_cdk and ic_cdk_timers are affected. If these canisters call a canister method, use timers or heartbeat, they will likely leak a small amount of memory on every such operation. In the worst case, this could lead to heap memory exhaustion triggered by an attacker. Motoko based canisters are not affected by the bug.
PatchesThe patch has been backported to all minor versions between >= 0.8.0, <= 0.15.0. The patched versions available are 0.8.2, 0.9.3, 0.10.1, 0.11.6, 0.12.2, 0.13.5, 0.14.1, 0.15.1 and their previous versions have been yanked. WorkaroundsThere are no known workarounds at the moment. Developers are recommended to upgrade their canister as soon as possible to the latest available patched version of ic_cdk to avoid running out of Wasm heap memory.
Upgrading the canisters (without updating `ic_cdk`) also frees the leaked memory but it's only a temporary solution.
References
Impacted products
| Vendor | Product | Version | |
|---|---|---|---|
| ▼ | Internet Computer | ic-cdk |
Version: 0.8.0 ≤ Version: 0.9.0 ≤ Version: 0.10.0 ≤ Version: 0.11.0 ≤ Version: 0.12.0 ≤ Version: 0.13.0 ≤ Version: 0.14.0 ≤ Version: 0.15.0 ≤ |
|
|
|||
{
"containers": {
"adp": [
{
"affected": [
{
"cpes": [
"cpe:2.3:a:internet_computer:ic-cdk:*:*:*:*:*:*:*:*"
],
"defaultStatus": "unknown",
"product": "ic-cdk",
"vendor": "internet_computer",
"versions": [
{
"lessThan": "0.8.2",
"status": "affected",
"version": "0.8.0",
"versionType": "semver"
},
{
"lessThan": "0.9.3",
"status": "affected",
"version": "0.9.0",
"versionType": "semver"
},
{
"lessThan": "0.10.1",
"status": "affected",
"version": "0.10.0",
"versionType": "semver"
},
{
"lessThan": "0.11.5",
"status": "affected",
"version": "0.11.0",
"versionType": "semver"
},
{
"lessThan": "0.12.2",
"status": "affected",
"version": "0.12.0",
"versionType": "semver"
},
{
"lessThan": "0.13.4",
"status": "affected",
"version": "0.13.0",
"versionType": "semver"
},
{
"lessThan": "0.14.1",
"status": "affected",
"version": "0.14.0",
"versionType": "semver"
},
{
"lessThan": "0.15.1",
"status": "affected",
"version": "0.15.0",
"versionType": "semver"
}
]
}
],
"metrics": [
{
"other": {
"content": {
"id": "CVE-2024-7884",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "yes"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2024-09-05T14:27:48.684901Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2024-09-05T14:42:09.085Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"collectionURL": "https://crates.io/crates/ic-cdk",
"defaultStatus": "unaffected",
"packageName": "ic-cdk",
"product": "ic-cdk",
"repo": "https://github.com/dfinity/cdk-rs",
"vendor": "Internet Computer",
"versions": [
{
"changes": [
{
"at": "0.8.2",
"status": "unaffected"
}
],
"lessThan": "0.8.2",
"status": "affected",
"version": "0.8.0",
"versionType": "semver"
},
{
"changes": [
{
"at": "0.9.3",
"status": "unaffected"
}
],
"lessThan": "0.9.3",
"status": "affected",
"version": "0.9.0",
"versionType": "semver"
},
{
"changes": [
{
"at": "0.10.1",
"status": "unaffected"
}
],
"lessThan": "0.10.1",
"status": "affected",
"version": "0.10.0",
"versionType": "semver"
},
{
"changes": [
{
"at": "0.11.6",
"status": "unaffected"
}
],
"lessThan": "0.11.5",
"status": "affected",
"version": "0.11.0",
"versionType": "semver"
},
{
"changes": [
{
"at": "0.12.2",
"status": "unaffected"
}
],
"lessThan": "0.12.2",
"status": "affected",
"version": "0.12.0",
"versionType": "semver"
},
{
"changes": [
{
"at": "0.13.5",
"status": "unaffected"
}
],
"lessThan": "0.13.4",
"status": "affected",
"version": "0.13.0",
"versionType": "semver"
},
{
"changes": [
{
"at": "0.14.1",
"status": "unaffected"
}
],
"lessThan": "0.14.1",
"status": "affected",
"version": "0.14.0",
"versionType": "semver"
},
{
"changes": [
{
"at": "0.15.1",
"status": "unaffected"
}
],
"lessThan": "0.15.1",
"status": "affected",
"version": "0.15.0",
"versionType": "semver"
}
]
}
],
"descriptions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "When a canister method is called via \u003ctt\u003eic_cdk::call*\u003c/tt\u003e , a new Future \u003ctt\u003eCallFuture\u0026nbsp;\u003c/tt\u003eis created and can be awaited by the caller to get the execution result. Internally, the state of the Future is tracked and stored in a struct called \u003ctt\u003eCallFutureState\u003c/tt\u003e. A bug in the polling implementation of the \u003ctt\u003eCallFuture\u003c/tt\u003e allows multiple references to be held for this internal state and not all references were dropped before the \u003ctt\u003eFuture\u003c/tt\u003e\u0026nbsp;is resolved. Since we have unaccounted references held, a copy of the internal state ended up being persisted in the canister\u0027s heap and thus causing a memory leak. \u003cbr\u003e\u003ch3\u003eImpact\u0026nbsp;\u003c/h3\u003eCanisters built in Rust with \u003ctt\u003eic_cdk\u003c/tt\u003e\u0026nbsp;and \u003ctt\u003eic_cdk_timers\u003c/tt\u003e\u0026nbsp;are affected. If these canisters call a canister method, use timers or heartbeat, they will likely leak a small amount of memory on every such operation. \u003cb\u003eIn the worst case, this could lead to heap memory exhaustion triggered by an attacker. \u003c/b\u003eMotoko based canisters are not affected by the bug.\u003cbr\u003e\u003ch3\u003ePatches\u003c/h3\u003eThe patch has been backported to all minor versions between \u003ctt\u003e\u0026gt;= 0.8.0, \u0026lt;= 0.15.0\u003c/tt\u003e. The patched versions available are \u003ctt\u003e0.8.2, 0.9.3, 0.10.1, 0.11.6, 0.12.2, 0.13.5, 0.14.1, 0.15.1 \u003c/tt\u003eand their previous versions have been yanked. \u003ch3\u003eWorkarounds\u003c/h3\u003eThere are no known workarounds at the moment. Developers are recommended to upgrade their canister as soon as possible to the latest available patched version of \u003ctt\u003eic_cdk\u003c/tt\u003e\u0026nbsp;to avoid running out of Wasm heap memory. \u003cbr\u003e\u003cblockquote\u003eUpgrading the canisters (without updating `ic_cdk`) also frees the leaked memory but it\u0027s only a temporary solution.\u003c/blockquote\u003e"
}
],
"value": "When a canister method is called via ic_cdk::call* , a new Future CallFuture\u00a0is created and can be awaited by the caller to get the execution result. Internally, the state of the Future is tracked and stored in a struct called CallFutureState. A bug in the polling implementation of the CallFuture allows multiple references to be held for this internal state and not all references were dropped before the Future\u00a0is resolved. Since we have unaccounted references held, a copy of the internal state ended up being persisted in the canister\u0027s heap and thus causing a memory leak. \nImpact\u00a0Canisters built in Rust with ic_cdk\u00a0and ic_cdk_timers\u00a0are affected. If these canisters call a canister method, use timers or heartbeat, they will likely leak a small amount of memory on every such operation. In the worst case, this could lead to heap memory exhaustion triggered by an attacker. Motoko based canisters are not affected by the bug.\nPatchesThe patch has been backported to all minor versions between \u003e= 0.8.0, \u003c= 0.15.0. The patched versions available are 0.8.2, 0.9.3, 0.10.1, 0.11.6, 0.12.2, 0.13.5, 0.14.1, 0.15.1 and their previous versions have been yanked. WorkaroundsThere are no known workarounds at the moment. Developers are recommended to upgrade their canister as soon as possible to the latest available patched version of ic_cdk\u00a0to avoid running out of Wasm heap memory. \nUpgrading the canisters (without updating `ic_cdk`) also frees the leaked memory but it\u0027s only a temporary solution."
}
],
"impacts": [
{
"capecId": "CAPEC-131",
"descriptions": [
{
"lang": "en",
"value": "CAPEC-131 Resource Leak Exposure"
}
]
}
],
"metrics": [
{
"cvssV3_1": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"format": "CVSS",
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-401",
"description": "CWE-401 Missing Release of Memory after Effective Lifetime",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2024-09-05T13:01:20.585Z",
"orgId": "6b35d637-e00f-4228-858c-b20ad6e1d07b",
"shortName": "Dfinity"
},
"references": [
{
"url": "https://github.com/dfinity/cdk-rs/pull/509"
},
{
"url": "https://docs.rs/ic-cdk/latest/ic_cdk/"
},
{
"url": "https://internetcomputer.org/docs/current/references/ic-interface-spec"
}
],
"source": {
"discovery": "UNKNOWN"
},
"title": "Memory leak when calling a canister method via `ic_cdk::call`",
"x_generator": {
"engine": "Vulnogram 0.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "6b35d637-e00f-4228-858c-b20ad6e1d07b",
"assignerShortName": "Dfinity",
"cveId": "CVE-2024-7884",
"datePublished": "2024-09-05T13:01:20.585Z",
"dateReserved": "2024-08-16T15:30:36.784Z",
"dateUpdated": "2024-09-05T14:42:09.085Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.1",
"vulnerability-lookup:meta": {
"fkie_nvd": {
"configurations": "[{\"nodes\": [{\"operator\": \"OR\", \"negate\": false, \"cpeMatch\": [{\"vulnerable\": true, \"criteria\": \"cpe:2.3:a:dfinity:canister_developer_kit_for_the_internet_computer:*:*:*:*:*:rust:*:*\", \"versionStartIncluding\": \"0.8.0\", \"versionEndExcluding\": \"0.8.2\", \"matchCriteriaId\": \"B282FC5B-DCC9-4E87-97A4-212E5B8F91EA\"}, {\"vulnerable\": true, \"criteria\": \"cpe:2.3:a:dfinity:canister_developer_kit_for_the_internet_computer:*:*:*:*:*:rust:*:*\", \"versionStartIncluding\": \"0.9.0\", \"versionEndExcluding\": \"0.9.3\", \"matchCriteriaId\": \"4D91E831-1BD4-4AC3-8F53-889BDD70FAD4\"}, {\"vulnerable\": true, \"criteria\": \"cpe:2.3:a:dfinity:canister_developer_kit_for_the_internet_computer:*:*:*:*:*:rust:*:*\", \"versionStartIncluding\": \"0.11.0\", \"versionEndExcluding\": \"0.11.6\", \"matchCriteriaId\": \"7EB88B2F-9AFC-4290-8BE0-CEB4CE2525CE\"}, {\"vulnerable\": true, \"criteria\": \"cpe:2.3:a:dfinity:canister_developer_kit_for_the_internet_computer:*:*:*:*:*:rust:*:*\", \"versionStartIncluding\": \"0.12.0\", \"versionEndExcluding\": \"0.12.2\", \"matchCriteriaId\": \"CD360546-4576-48E9-8F00-BF478698CEC3\"}, {\"vulnerable\": true, \"criteria\": \"cpe:2.3:a:dfinity:canister_developer_kit_for_the_internet_computer:*:*:*:*:*:rust:*:*\", \"versionStartIncluding\": \"0.13.0\", \"versionEndExcluding\": \"0.13.5\", \"matchCriteriaId\": \"C5157DF4-58E6-4F7B-A4A7-D7D2800DF5DB\"}, {\"vulnerable\": true, \"criteria\": \"cpe:2.3:a:dfinity:canister_developer_kit_for_the_internet_computer:0.10.0:*:*:*:*:rust:*:*\", \"matchCriteriaId\": \"D4C3CD14-0CDD-4D0A-A698-FA008BF854C0\"}, {\"vulnerable\": true, \"criteria\": \"cpe:2.3:a:dfinity:canister_developer_kit_for_the_internet_computer:0.14.0:*:*:*:*:rust:*:*\", \"matchCriteriaId\": \"8523743A-88F9-4D42-945A-F79BA5AB91D1\"}, {\"vulnerable\": true, \"criteria\": \"cpe:2.3:a:dfinity:canister_developer_kit_for_the_internet_computer:0.15.0:*:*:*:*:rust:*:*\", \"matchCriteriaId\": \"0C94A6D7-8B8A-493F-BA58-2D72300F97B5\"}]}]}]",
"descriptions": "[{\"lang\": \"en\", \"value\": \"When a canister method is called via ic_cdk::call* , a new Future CallFuture\\u00a0is created and can be awaited by the caller to get the execution result. Internally, the state of the Future is tracked and stored in a struct called CallFutureState. A bug in the polling implementation of the CallFuture allows multiple references to be held for this internal state and not all references were dropped before the Future\\u00a0is resolved. Since we have unaccounted references held, a copy of the internal state ended up being persisted in the canister\u0027s heap and thus causing a memory leak. \\nImpact\\u00a0Canisters built in Rust with ic_cdk\\u00a0and ic_cdk_timers\\u00a0are affected. If these canisters call a canister method, use timers or heartbeat, they will likely leak a small amount of memory on every such operation. In the worst case, this could lead to heap memory exhaustion triggered by an attacker. Motoko based canisters are not affected by the bug.\\nPatchesThe patch has been backported to all minor versions between \u003e= 0.8.0, \u003c= 0.15.0. The patched versions available are 0.8.2, 0.9.3, 0.10.1, 0.11.6, 0.12.2, 0.13.5, 0.14.1, 0.15.1 and their previous versions have been yanked. WorkaroundsThere are no known workarounds at the moment. Developers are recommended to upgrade their canister as soon as possible to the latest available patched version of ic_cdk\\u00a0to avoid running out of Wasm heap memory. \\nUpgrading the canisters (without updating `ic_cdk`) also frees the leaked memory but it\u0027s only a temporary solution.\"}, {\"lang\": \"es\", \"value\": \"Cuando se llama a un m\\u00e9todo de contenedor a trav\\u00e9s de ic_cdk::call* , se crea un nuevo Future CallFuture y el llamador puede esperar para obtener el resultado de la ejecuci\\u00f3n. Internamente, el estado del Future se rastrea y se almacena en una estructura llamada CallFutureState. Un error en la implementaci\\u00f3n de sondeo de CallFuture permite que se mantengan m\\u00faltiples referencias para este estado interno y no todas las referencias se descartaron antes de que se resolviera el Future. Dado que tenemos referencias no contabilizadas retenidas, una copia del estado interno termin\\u00f3 siendo persistente en el mont\\u00f3n del contenedor y, por lo tanto, caus\\u00f3 una p\\u00e9rdida de memoria. Impacto Los contenedores creados en Rust con ic_cdk e ic_cdk_timers se ven afectados. Si estos contenedores llaman a un m\\u00e9todo de contenedor, usan temporizadores o latidos, es probable que pierdan una peque\\u00f1a cantidad de memoria en cada una de esas operaciones. En el peor de los casos, esto podr\\u00eda provocar el agotamiento de la memoria del mont\\u00f3n activado por un atacante. Los contenedores basados en Motoko no se ven afectados por el error. ParchesEl parche ha sido retroportado a todas las versiones menores entre \u0026gt;= 0.8.0, \u0026lt;= 0.15.0. Las versiones parcheadas disponibles son 0.8.2, 0.9.3, 0.10.1, 0.11.6, 0.12.2, 0.13.5, 0.14.1, 0.15.1 y sus versiones anteriores han sido eliminadas. Workarounds, no hay soluciones workarounds en este momento. Se recomienda a los desarrolladores que actualicen su contenedor lo antes posible a la \\u00faltima versi\\u00f3n parcheada disponible de ic_cdk para evitar quedarse sin memoria del mont\\u00f3n de Wasm. Actualizar los contenedores (sin actualizar `ic_cdk`) tambi\\u00e9n libera la memoria filtrada, pero es solo una soluci\\u00f3n temporal.\"}]",
"id": "CVE-2024-7884",
"lastModified": "2024-09-12T20:47:13.387",
"metrics": "{\"cvssMetricV31\": [{\"source\": \"6b35d637-e00f-4228-858c-b20ad6e1d07b\", \"type\": \"Secondary\", \"cvssData\": {\"version\": \"3.1\", \"vectorString\": \"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H\", \"baseScore\": 7.5, \"baseSeverity\": \"HIGH\", \"attackVector\": \"NETWORK\", \"attackComplexity\": \"LOW\", \"privilegesRequired\": \"NONE\", \"userInteraction\": \"NONE\", \"scope\": \"UNCHANGED\", \"confidentialityImpact\": \"NONE\", \"integrityImpact\": \"NONE\", \"availabilityImpact\": \"HIGH\"}, \"exploitabilityScore\": 3.9, \"impactScore\": 3.6}, {\"source\": \"nvd@nist.gov\", \"type\": \"Primary\", \"cvssData\": {\"version\": \"3.1\", \"vectorString\": \"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H\", \"baseScore\": 7.5, \"baseSeverity\": \"HIGH\", \"attackVector\": \"NETWORK\", \"attackComplexity\": \"LOW\", \"privilegesRequired\": \"NONE\", \"userInteraction\": \"NONE\", \"scope\": \"UNCHANGED\", \"confidentialityImpact\": \"NONE\", \"integrityImpact\": \"NONE\", \"availabilityImpact\": \"HIGH\"}, \"exploitabilityScore\": 3.9, \"impactScore\": 3.6}]}",
"published": "2024-09-05T13:15:11.390",
"references": "[{\"url\": \"https://docs.rs/ic-cdk/latest/ic_cdk/\", \"source\": \"6b35d637-e00f-4228-858c-b20ad6e1d07b\", \"tags\": [\"Product\"]}, {\"url\": \"https://github.com/dfinity/cdk-rs/pull/509\", \"source\": \"6b35d637-e00f-4228-858c-b20ad6e1d07b\", \"tags\": [\"Issue Tracking\", \"Patch\"]}, {\"url\": \"https://internetcomputer.org/docs/current/references/ic-interface-spec\", \"source\": \"6b35d637-e00f-4228-858c-b20ad6e1d07b\", \"tags\": [\"Product\"]}]",
"sourceIdentifier": "6b35d637-e00f-4228-858c-b20ad6e1d07b",
"vulnStatus": "Analyzed",
"weaknesses": "[{\"source\": \"6b35d637-e00f-4228-858c-b20ad6e1d07b\", \"type\": \"Secondary\", \"description\": [{\"lang\": \"en\", \"value\": \"CWE-401\"}]}, {\"source\": \"nvd@nist.gov\", \"type\": \"Primary\", \"description\": [{\"lang\": \"en\", \"value\": \"CWE-401\"}]}]"
},
"nvd": "{\"cve\":{\"id\":\"CVE-2024-7884\",\"sourceIdentifier\":\"6b35d637-e00f-4228-858c-b20ad6e1d07b\",\"published\":\"2024-09-05T13:15:11.390\",\"lastModified\":\"2024-09-12T20:47:13.387\",\"vulnStatus\":\"Analyzed\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"When a canister method is called via ic_cdk::call* , a new Future CallFuture\u00a0is created and can be awaited by the caller to get the execution result. Internally, the state of the Future is tracked and stored in a struct called CallFutureState. A bug in the polling implementation of the CallFuture allows multiple references to be held for this internal state and not all references were dropped before the Future\u00a0is resolved. Since we have unaccounted references held, a copy of the internal state ended up being persisted in the canister\u0027s heap and thus causing a memory leak. \\nImpact\u00a0Canisters built in Rust with ic_cdk\u00a0and ic_cdk_timers\u00a0are affected. If these canisters call a canister method, use timers or heartbeat, they will likely leak a small amount of memory on every such operation. In the worst case, this could lead to heap memory exhaustion triggered by an attacker. Motoko based canisters are not affected by the bug.\\nPatchesThe patch has been backported to all minor versions between \u003e= 0.8.0, \u003c= 0.15.0. The patched versions available are 0.8.2, 0.9.3, 0.10.1, 0.11.6, 0.12.2, 0.13.5, 0.14.1, 0.15.1 and their previous versions have been yanked. WorkaroundsThere are no known workarounds at the moment. Developers are recommended to upgrade their canister as soon as possible to the latest available patched version of ic_cdk\u00a0to avoid running out of Wasm heap memory. \\nUpgrading the canisters (without updating `ic_cdk`) also frees the leaked memory but it\u0027s only a temporary solution.\"},{\"lang\":\"es\",\"value\":\"Cuando se llama a un m\u00e9todo de contenedor a trav\u00e9s de ic_cdk::call* , se crea un nuevo Future CallFuture y el llamador puede esperar para obtener el resultado de la ejecuci\u00f3n. Internamente, el estado del Future se rastrea y se almacena en una estructura llamada CallFutureState. Un error en la implementaci\u00f3n de sondeo de CallFuture permite que se mantengan m\u00faltiples referencias para este estado interno y no todas las referencias se descartaron antes de que se resolviera el Future. Dado que tenemos referencias no contabilizadas retenidas, una copia del estado interno termin\u00f3 siendo persistente en el mont\u00f3n del contenedor y, por lo tanto, caus\u00f3 una p\u00e9rdida de memoria. Impacto Los contenedores creados en Rust con ic_cdk e ic_cdk_timers se ven afectados. Si estos contenedores llaman a un m\u00e9todo de contenedor, usan temporizadores o latidos, es probable que pierdan una peque\u00f1a cantidad de memoria en cada una de esas operaciones. En el peor de los casos, esto podr\u00eda provocar el agotamiento de la memoria del mont\u00f3n activado por un atacante. Los contenedores basados en Motoko no se ven afectados por el error. ParchesEl parche ha sido retroportado a todas las versiones menores entre \u0026gt;= 0.8.0, \u0026lt;= 0.15.0. Las versiones parcheadas disponibles son 0.8.2, 0.9.3, 0.10.1, 0.11.6, 0.12.2, 0.13.5, 0.14.1, 0.15.1 y sus versiones anteriores han sido eliminadas. Workarounds, no hay soluciones workarounds en este momento. Se recomienda a los desarrolladores que actualicen su contenedor lo antes posible a la \u00faltima versi\u00f3n parcheada disponible de ic_cdk para evitar quedarse sin memoria del mont\u00f3n de Wasm. Actualizar los contenedores (sin actualizar `ic_cdk`) tambi\u00e9n libera la memoria filtrada, pero es solo una soluci\u00f3n temporal.\"}],\"metrics\":{\"cvssMetricV31\":[{\"source\":\"6b35d637-e00f-4228-858c-b20ad6e1d07b\",\"type\":\"Secondary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H\",\"baseScore\":7.5,\"baseSeverity\":\"HIGH\",\"attackVector\":\"NETWORK\",\"attackComplexity\":\"LOW\",\"privilegesRequired\":\"NONE\",\"userInteraction\":\"NONE\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"NONE\",\"integrityImpact\":\"NONE\",\"availabilityImpact\":\"HIGH\"},\"exploitabilityScore\":3.9,\"impactScore\":3.6},{\"source\":\"nvd@nist.gov\",\"type\":\"Primary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H\",\"baseScore\":7.5,\"baseSeverity\":\"HIGH\",\"attackVector\":\"NETWORK\",\"attackComplexity\":\"LOW\",\"privilegesRequired\":\"NONE\",\"userInteraction\":\"NONE\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"NONE\",\"integrityImpact\":\"NONE\",\"availabilityImpact\":\"HIGH\"},\"exploitabilityScore\":3.9,\"impactScore\":3.6}]},\"weaknesses\":[{\"source\":\"6b35d637-e00f-4228-858c-b20ad6e1d07b\",\"type\":\"Secondary\",\"description\":[{\"lang\":\"en\",\"value\":\"CWE-401\"}]},{\"source\":\"nvd@nist.gov\",\"type\":\"Primary\",\"description\":[{\"lang\":\"en\",\"value\":\"CWE-401\"}]}],\"configurations\":[{\"nodes\":[{\"operator\":\"OR\",\"negate\":false,\"cpeMatch\":[{\"vulnerable\":true,\"criteria\":\"cpe:2.3:a:dfinity:canister_developer_kit_for_the_internet_computer:*:*:*:*:*:rust:*:*\",\"versionStartIncluding\":\"0.8.0\",\"versionEndExcluding\":\"0.8.2\",\"matchCriteriaId\":\"B282FC5B-DCC9-4E87-97A4-212E5B8F91EA\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:a:dfinity:canister_developer_kit_for_the_internet_computer:*:*:*:*:*:rust:*:*\",\"versionStartIncluding\":\"0.9.0\",\"versionEndExcluding\":\"0.9.3\",\"matchCriteriaId\":\"4D91E831-1BD4-4AC3-8F53-889BDD70FAD4\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:a:dfinity:canister_developer_kit_for_the_internet_computer:*:*:*:*:*:rust:*:*\",\"versionStartIncluding\":\"0.11.0\",\"versionEndExcluding\":\"0.11.6\",\"matchCriteriaId\":\"7EB88B2F-9AFC-4290-8BE0-CEB4CE2525CE\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:a:dfinity:canister_developer_kit_for_the_internet_computer:*:*:*:*:*:rust:*:*\",\"versionStartIncluding\":\"0.12.0\",\"versionEndExcluding\":\"0.12.2\",\"matchCriteriaId\":\"CD360546-4576-48E9-8F00-BF478698CEC3\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:a:dfinity:canister_developer_kit_for_the_internet_computer:*:*:*:*:*:rust:*:*\",\"versionStartIncluding\":\"0.13.0\",\"versionEndExcluding\":\"0.13.5\",\"matchCriteriaId\":\"C5157DF4-58E6-4F7B-A4A7-D7D2800DF5DB\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:a:dfinity:canister_developer_kit_for_the_internet_computer:0.10.0:*:*:*:*:rust:*:*\",\"matchCriteriaId\":\"D4C3CD14-0CDD-4D0A-A698-FA008BF854C0\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:a:dfinity:canister_developer_kit_for_the_internet_computer:0.14.0:*:*:*:*:rust:*:*\",\"matchCriteriaId\":\"8523743A-88F9-4D42-945A-F79BA5AB91D1\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:a:dfinity:canister_developer_kit_for_the_internet_computer:0.15.0:*:*:*:*:rust:*:*\",\"matchCriteriaId\":\"0C94A6D7-8B8A-493F-BA58-2D72300F97B5\"}]}]}],\"references\":[{\"url\":\"https://docs.rs/ic-cdk/latest/ic_cdk/\",\"source\":\"6b35d637-e00f-4228-858c-b20ad6e1d07b\",\"tags\":[\"Product\"]},{\"url\":\"https://github.com/dfinity/cdk-rs/pull/509\",\"source\":\"6b35d637-e00f-4228-858c-b20ad6e1d07b\",\"tags\":[\"Issue Tracking\",\"Patch\"]},{\"url\":\"https://internetcomputer.org/docs/current/references/ic-interface-spec\",\"source\":\"6b35d637-e00f-4228-858c-b20ad6e1d07b\",\"tags\":[\"Product\"]}]}}",
"vulnrichment": {
"containers": "{\"adp\": [{\"title\": \"CISA ADP Vulnrichment\", \"metrics\": [{\"other\": {\"type\": \"ssvc\", \"content\": {\"id\": \"CVE-2024-7884\", \"role\": \"CISA Coordinator\", \"options\": [{\"Exploitation\": \"none\"}, {\"Automatable\": \"yes\"}, {\"Technical Impact\": \"partial\"}], \"version\": \"2.0.3\", \"timestamp\": \"2024-09-05T14:27:48.684901Z\"}}}], \"affected\": [{\"cpes\": [\"cpe:2.3:a:internet_computer:ic-cdk:*:*:*:*:*:*:*:*\"], \"vendor\": \"internet_computer\", \"product\": \"ic-cdk\", \"versions\": [{\"status\": \"affected\", \"version\": \"0.8.0\", \"lessThan\": \"0.8.2\", \"versionType\": \"semver\"}, {\"status\": \"affected\", \"version\": \"0.9.0\", \"lessThan\": \"0.9.3\", \"versionType\": \"semver\"}, {\"status\": \"affected\", \"version\": \"0.10.0\", \"lessThan\": \"0.10.1\", \"versionType\": \"semver\"}, {\"status\": \"affected\", \"version\": \"0.11.0\", \"lessThan\": \"0.11.5\", \"versionType\": \"semver\"}, {\"status\": \"affected\", \"version\": \"0.12.0\", \"lessThan\": \"0.12.2\", \"versionType\": \"semver\"}, {\"status\": \"affected\", \"version\": \"0.13.0\", \"lessThan\": \"0.13.4\", \"versionType\": \"semver\"}, {\"status\": \"affected\", \"version\": \"0.14.0\", \"lessThan\": \"0.14.1\", \"versionType\": \"semver\"}, {\"status\": \"affected\", \"version\": \"0.15.0\", \"lessThan\": \"0.15.1\", \"versionType\": \"semver\"}], \"defaultStatus\": \"unknown\"}], \"providerMetadata\": {\"orgId\": \"134c704f-9b21-4f2e-91b3-4a467353bcc0\", \"shortName\": \"CISA-ADP\", \"dateUpdated\": \"2024-09-05T14:42:00.032Z\"}}], \"cna\": {\"title\": \"Memory leak when calling a canister method via `ic_cdk::call`\", \"source\": {\"discovery\": \"UNKNOWN\"}, \"impacts\": [{\"capecId\": \"CAPEC-131\", \"descriptions\": [{\"lang\": \"en\", \"value\": \"CAPEC-131 Resource Leak Exposure\"}]}], \"metrics\": [{\"format\": \"CVSS\", \"cvssV3_1\": {\"scope\": \"UNCHANGED\", \"version\": \"3.1\", \"baseScore\": 7.5, \"attackVector\": \"NETWORK\", \"baseSeverity\": \"HIGH\", \"vectorString\": \"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H\", \"integrityImpact\": \"NONE\", \"userInteraction\": \"NONE\", \"attackComplexity\": \"LOW\", \"availabilityImpact\": \"HIGH\", \"privilegesRequired\": \"NONE\", \"confidentialityImpact\": \"NONE\"}, \"scenarios\": [{\"lang\": \"en\", \"value\": \"GENERAL\"}]}], \"affected\": [{\"repo\": \"https://github.com/dfinity/cdk-rs\", \"vendor\": \"Internet Computer\", \"product\": \"ic-cdk\", \"versions\": [{\"status\": \"affected\", \"changes\": [{\"at\": \"0.8.2\", \"status\": \"unaffected\"}], \"version\": \"0.8.0\", \"lessThan\": \"0.8.2\", \"versionType\": \"semver\"}, {\"status\": \"affected\", \"changes\": [{\"at\": \"0.9.3\", \"status\": \"unaffected\"}], \"version\": \"0.9.0\", \"lessThan\": \"0.9.3\", \"versionType\": \"semver\"}, {\"status\": \"affected\", \"changes\": [{\"at\": \"0.10.1\", \"status\": \"unaffected\"}], \"version\": \"0.10.0\", \"lessThan\": \"0.10.1\", \"versionType\": \"semver\"}, {\"status\": \"affected\", \"changes\": [{\"at\": \"0.11.6\", \"status\": \"unaffected\"}], \"version\": \"0.11.0\", \"lessThan\": \"0.11.5\", \"versionType\": \"semver\"}, {\"status\": \"affected\", \"changes\": [{\"at\": \"0.12.2\", \"status\": \"unaffected\"}], \"version\": \"0.12.0\", \"lessThan\": \"0.12.2\", \"versionType\": \"semver\"}, {\"status\": \"affected\", \"changes\": [{\"at\": \"0.13.5\", \"status\": \"unaffected\"}], \"version\": \"0.13.0\", \"lessThan\": \"0.13.4\", \"versionType\": \"semver\"}, {\"status\": \"affected\", \"changes\": [{\"at\": \"0.14.1\", \"status\": \"unaffected\"}], \"version\": \"0.14.0\", \"lessThan\": \"0.14.1\", \"versionType\": \"semver\"}, {\"status\": \"affected\", \"changes\": [{\"at\": \"0.15.1\", \"status\": \"unaffected\"}], \"version\": \"0.15.0\", \"lessThan\": \"0.15.1\", \"versionType\": \"semver\"}], \"packageName\": \"ic-cdk\", \"collectionURL\": \"https://crates.io/crates/ic-cdk\", \"defaultStatus\": \"unaffected\"}], \"references\": [{\"url\": \"https://github.com/dfinity/cdk-rs/pull/509\"}, {\"url\": \"https://docs.rs/ic-cdk/latest/ic_cdk/\"}, {\"url\": \"https://internetcomputer.org/docs/current/references/ic-interface-spec\"}], \"x_generator\": {\"engine\": \"Vulnogram 0.2.0\"}, \"descriptions\": [{\"lang\": \"en\", \"value\": \"When a canister method is called via ic_cdk::call* , a new Future CallFuture\\u00a0is created and can be awaited by the caller to get the execution result. Internally, the state of the Future is tracked and stored in a struct called CallFutureState. A bug in the polling implementation of the CallFuture allows multiple references to be held for this internal state and not all references were dropped before the Future\\u00a0is resolved. Since we have unaccounted references held, a copy of the internal state ended up being persisted in the canister\u0027s heap and thus causing a memory leak. \\nImpact\\u00a0Canisters built in Rust with ic_cdk\\u00a0and ic_cdk_timers\\u00a0are affected. If these canisters call a canister method, use timers or heartbeat, they will likely leak a small amount of memory on every such operation. In the worst case, this could lead to heap memory exhaustion triggered by an attacker. Motoko based canisters are not affected by the bug.\\nPatchesThe patch has been backported to all minor versions between \u003e= 0.8.0, \u003c= 0.15.0. The patched versions available are 0.8.2, 0.9.3, 0.10.1, 0.11.6, 0.12.2, 0.13.5, 0.14.1, 0.15.1 and their previous versions have been yanked. WorkaroundsThere are no known workarounds at the moment. Developers are recommended to upgrade their canister as soon as possible to the latest available patched version of ic_cdk\\u00a0to avoid running out of Wasm heap memory. \\nUpgrading the canisters (without updating `ic_cdk`) also frees the leaked memory but it\u0027s only a temporary solution.\", \"supportingMedia\": [{\"type\": \"text/html\", \"value\": \"When a canister method is called via \u003ctt\u003eic_cdk::call*\u003c/tt\u003e , a new Future \u003ctt\u003eCallFuture\u0026nbsp;\u003c/tt\u003eis created and can be awaited by the caller to get the execution result. Internally, the state of the Future is tracked and stored in a struct called \u003ctt\u003eCallFutureState\u003c/tt\u003e. A bug in the polling implementation of the \u003ctt\u003eCallFuture\u003c/tt\u003e allows multiple references to be held for this internal state and not all references were dropped before the \u003ctt\u003eFuture\u003c/tt\u003e\u0026nbsp;is resolved. Since we have unaccounted references held, a copy of the internal state ended up being persisted in the canister\u0027s heap and thus causing a memory leak. \u003cbr\u003e\u003ch3\u003eImpact\u0026nbsp;\u003c/h3\u003eCanisters built in Rust with \u003ctt\u003eic_cdk\u003c/tt\u003e\u0026nbsp;and \u003ctt\u003eic_cdk_timers\u003c/tt\u003e\u0026nbsp;are affected. If these canisters call a canister method, use timers or heartbeat, they will likely leak a small amount of memory on every such operation. \u003cb\u003eIn the worst case, this could lead to heap memory exhaustion triggered by an attacker. \u003c/b\u003eMotoko based canisters are not affected by the bug.\u003cbr\u003e\u003ch3\u003ePatches\u003c/h3\u003eThe patch has been backported to all minor versions between \u003ctt\u003e\u0026gt;= 0.8.0, \u0026lt;= 0.15.0\u003c/tt\u003e. The patched versions available are \u003ctt\u003e0.8.2, 0.9.3, 0.10.1, 0.11.6, 0.12.2, 0.13.5, 0.14.1, 0.15.1 \u003c/tt\u003eand their previous versions have been yanked. \u003ch3\u003eWorkarounds\u003c/h3\u003eThere are no known workarounds at the moment. Developers are recommended to upgrade their canister as soon as possible to the latest available patched version of \u003ctt\u003eic_cdk\u003c/tt\u003e\u0026nbsp;to avoid running out of Wasm heap memory. \u003cbr\u003e\u003cblockquote\u003eUpgrading the canisters (without updating `ic_cdk`) also frees the leaked memory but it\u0027s only a temporary solution.\u003c/blockquote\u003e\", \"base64\": false}]}], \"problemTypes\": [{\"descriptions\": [{\"lang\": \"en\", \"type\": \"CWE\", \"cweId\": \"CWE-401\", \"description\": \"CWE-401 Missing Release of Memory after Effective Lifetime\"}]}], \"providerMetadata\": {\"orgId\": \"6b35d637-e00f-4228-858c-b20ad6e1d07b\", \"shortName\": \"Dfinity\", \"dateUpdated\": \"2024-09-05T13:01:20.585Z\"}}}",
"cveMetadata": "{\"cveId\": \"CVE-2024-7884\", \"state\": \"PUBLISHED\", \"dateUpdated\": \"2024-09-05T14:42:09.085Z\", \"dateReserved\": \"2024-08-16T15:30:36.784Z\", \"assignerOrgId\": \"6b35d637-e00f-4228-858c-b20ad6e1d07b\", \"datePublished\": \"2024-09-05T13:01:20.585Z\", \"assignerShortName\": \"Dfinity\"}",
"dataType": "CVE_RECORD",
"dataVersion": "5.1"
}
}
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.