Skip to content

elrond-go MultiESDTNFTTransfer call on a SC address with missing function name

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

Package

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

Affected versions

<= 1.3.33

Patched versions

1.3.34

Description

Impact

Anyone who uses elrond-go to process blocks (historical or actual) that contains a transaction like this: MultiESDTNFTTransfer@01@54444558544b4b5955532d323631626138@00@0793afc18c8da2ca@ (mind the missing function name after the last @)
Basic functionality like p2p messaging, storage, API requests and such are unaffected.

Patches

Patch v1.3.34 or higher

Workarounds

No workarounds

References

For future reference, one can observe the following integration test:
[provide the link to the integration test]

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 to the GitHub Advisory Database Sep 1, 2022
Reviewed Sep 1, 2022
Published by the National Vulnerability Database Sep 6, 2022
Last updated Jan 30, 2023

Severity

High

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
None
Integrity
High
Availability
None

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:N/I:H/A:N

EPSS score

0.070%
(32nd percentile)

Weaknesses

CVE ID

CVE-2022-36058

GHSA ID

GHSA-qf7j-25g9-r63f

Source code

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