Skip to content

Elrond-go has improper initialization

Critical severity GitHub Reviewed Published Aug 29, 2022 in multiversx/mx-chain-go • Updated Jan 27, 2023

Package

gomod github.com/ElrondNetwork/elrond-go (Go)

Affected versions

<= 1.3.34

Patched versions

1.3.35

Description

Impact

Read only calls between contracts can generate smart contracts results. For example, if contract A calls in read only mode contract B and the called function will make changes upon the contract's B state, the state will be altered for contract B as if the call was not made in the read-only mode. This can lead to some effects not designed by the original smart contracts programmers.

Patches

Patch v1.3.35 or higher

Workarounds

No workaround

References

For future reference and understanding of this issue, anyone can check this integration test https://github.com/ElrondNetwork/elrond-go/blob/8e402fa6d7e91e779980122d3798b2bf50892945/integrationTests/vm/txsFee/asyncESDT_test.go#L452 that proves the fix and prevents a future code regression.

For more information

If you have any questions or comments about this advisory:

References

@iulianpascalau iulianpascalau published to multiversx/mx-chain-go Aug 29, 2022
Published by the National Vulnerability Database Sep 6, 2022
Published to the GitHub Advisory Database Sep 16, 2022
Reviewed Sep 16, 2022
Last updated Jan 27, 2023

Severity

Critical

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS score

0.407%
(74th percentile)

Weaknesses

CVE ID

CVE-2022-36061

GHSA ID

GHSA-mv8x-668m-53fg

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.