Advisory

GHSA-853p-5678-hv8f

Also known as: CVE-2023-34449

Summary

ink! vulnerable to incorrect decoding of storage value when using DelegateCall

Details

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:

// 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::<DefaultEnvironment>()
        .delegate(callee_code_hash)
        .exec_input(ExecutionInput::new(Selector::new(ink::selector_bytes!(
            "get_value"
        ))))
        .returns::<u128>()
        .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 uints 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.

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2023-06-14 20:11 UTC
Modified
2026-09-10 03:50 UTC

Affected packages and fixes

ink

crates.io · All systems

Affected

  • introduced 4.0.0, fixed 4.2.1 (semver)

Fixed versions

4.2.1

Fix

  • Fixed version 4.2.1
    cargo update -p ink --precise 4.2.1

ink_env

crates.io · All systems

Affected

  • introduced 4.0.0, fixed 4.2.1 (semver)

Fixed versions

4.2.1

Fix

  • Fixed version 4.2.1
    cargo update -p ink_env --precise 4.2.1

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences