CVE-2023-34449
Assigner: GitHub_M
Published: 2023-06-14T20:10:54.842Z
State: PUBLISHED
title: ink! vulnerable to incorrect decoding of storage value when using `DelegateCall`
problemTypes: descriptions: cweId: CWE-754
description: CWE-754: Improper Check for Unusual or Exceptional Conditions
type: CWE
descriptions: cweId: CWE-253
description: CWE-253: Incorrect Check of Function Return Value
type: CWE
metrics: cvssV3_1: attackComplexity: LOW
attackVector: NETWORK
availabilityImpact: NONE
baseScore: 5.3
baseSeverity: MEDIUM
confidentialityImpact: NONE
integrityImpact: LOW
privilegesRequired: NONE
scope: UNCHANGED
userInteraction: NONE
vectorString: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
version: 3.1
affected: vendor: paritytech
product: ink
versions: version: >= 4.0.0, < 4.2.1
status: affected
descriptions: value: 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.
source: advisory: GHSA-853p-5678-hv8f
discovery: UNKNOWN