Skip to content

Elrond-GO processing: fallback search of SCRs when not found in the main cache

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

Package

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

Affected versions

<= 1.3.48

Patched versions

1.3.50

Description

Impact

Processing issue, nodes are affected when trying to process a cross-shard relayed transaction with a smart contract deploy transaction data. The problem was a bad correlation between the transaction caches and the processing component. If the above-mentioned transaction was sent with more gas than required, the smart contract result (SCR transaction) that should have returned the leftover gas, would have been wrongly added to a cache that the processing unit did not consider. The node stopped notarizing metachain blocks. The fix was actually to extend the SCR transaction search in all other caches if it wasn't found in the correct (expected) sharded-cache.

Patches

All versions >= v1.3.50 will contain this patch

Workarounds

For the moment there is no workaround

References

N/A

For more information

If you have any questions or comments about this advisory:

References

@iulianpascalau iulianpascalau published to multiversx/mx-chain-go Dec 23, 2022
Published by the National Vulnerability Database Dec 28, 2022
Published to the GitHub Advisory Database Dec 30, 2022
Reviewed Dec 30, 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
Changed
Confidentiality
None
Integrity
Low
Availability
Low

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

EPSS score

0.105%
(44th percentile)

Weaknesses

CVE ID

CVE-2022-46173

GHSA ID

GHSA-p228-4mrh-ww7r

Source code

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