ink! vulnerable to incorrect decoding of storage value when using `DelegateCall`
13Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 5.3epss 1.0%
exploitation probability
1.0%top 41% of all CVEs
observed exploitation
nono source reports it
ink! is an embedded domain specific language to write smart contracts in Rust for blockchains built on the Substrate framework. Starting in version 4.0.0 and prior to version 4.2.1, the return value when using delegate call mechanics, either through `CallBuilder::delegate` or `ink_env::invoke_contract_delegate`, is decoded incorrectly. This bug was related to the mechanics around decoding a call's return buffer, which was changed as part of pull request 1450. Since this feature was only released in ink! 4.0.0, no previous versions are affected. Users who have an ink! 4.x series contract should upgrade to 4.2.1 to receive a patch.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Affected products
paritytech · inkReferences
https://docs.rs/ink_env/4.2.0/ink_env/call/struct.CallBuilder.html#method.delegatehttps://docs.rs/ink_env/4.2.0/ink_env/fn.invoke_contract_delegate.htmlhttps://github.com/paritytech/ink/commit/f1407ee9f87e5f64d467a22d26ee88f61db7f3dbhttps://github.com/paritytech/ink/pull/1450https://github.com/paritytech/ink/security/advisories/GHSA-853p-5678-hv8f