GitHub Advisoryadvisory · crates.io
GHSA-853p-5678-hv8f ink! vulnerable to incorrect decoding of storage value when using `DelegateCall`
MEDIUM
Official page ↗
- Aliases
- CVE-2023-34449
- Ecosystem
- crates.io
- Packages
- ink, ink_env
- Severity
- Moderate
- CVSS vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
- Weaknesses
- CWE-253, CWE-754
- Reviewed
- 2023-06-14
Affected packages
• crates.io ink: >= 4.0.0, < 4.2.1 → fixed in 4.2.1
• crates.io ink_env: >= 4.0.0, < 4.2.1 → fixed in 4.2.1
Description
Summary
The return value when using delegate call mechanics, either through `CallBuilder::delegate` or `ink_env::invoke_contract_delegate`, is being decoded incorrectly.
Description
Consider this minimal example:
```rust
// First contract, this will be performing a delegate call to the `Callee`.
[ink(storage)]
pub struct Caller {
value: u128,
}
[ink(message)]
pub fn get_value(&self, callee_code_hash: Hash) -> u128 {
let result = build_call::()
.delegate(callee_code_hash)
.exec_input(ExecutionInput::new(Selector::new(ink::selector_bytes!(
"get_value"
))))
.returns::()
.invoke();
result
}
// Different contract, using this code hash for the delegate call.
[ink(storage)]
pub struct Callee {
value: u128,
}
[ink(message)]
pub fn get_value(&self) -> u128 {
self.value
}
```
In this example we are executing the `Callee` code in the context of the `Caller` contract. This means we'll be using the storage values of the `Caller` contract.
Running this code we expect the delegate call to return `value` as it was stored in the `Caller` contract. However, due to the reported bug a different value is returned (for the case of `uint`s it is `256` times the expected value).
Impact
After conducting an analysis of the on-chain deployments of ink! contracts on Astar, Shiden, Aleph Zero, Amplitude and Pendulum, we have found that no contracts on those chains have been affected by the issue.
This bug was related to the mechanics around decoding a call's return buffer, which was changed as part of https://github.com/paritytech/ink/pull/1450. Since this feature was only released in ink! 4.0.0 no previous versions are affected.
Mitigations
If you have an ink! 4.x series contract, please update it to the 4.2.1 patch release that we just published.
Credits
Thank you Facundo Lerena from CoinFabrik for reporting this problem in a well-structured and responsible way.
Related
Alias · CVE (1)
- CVE-2023-34449 ink! vulnerability
References
- https://github.com/paritytech/ink/security/advisories/GHSA-853p-5678-hv8f web
- https://nvd.nist.gov/vuln/detail/CVE-2023-34449 advisory
- https://github.com/paritytech/ink/pull/1450 web
- https://github.com/paritytech/ink/commit/f1407ee9f87e5f64d467a22d26ee88f61db7f3db web
- https://docs.rs/ink_env/4.2.0/ink_env/call/struct.CallBuilder.html#method.delegate web
- https://docs.rs/ink_env/4.2.0/ink_env/fn.invoke_contract_delegate.html web
- https://github.com/paritytech/ink package