CVE-2022-46173: Elrond go Processing: fallback search of SCRs when not found in the main cache

Severity: medium (CVSS 6.5 v3.1)
Exploited in the wild: not listed in CISA KEV
EPSS: 0.8% probability of exploitation in the next 30 days
Public exploit or detection template: none known
Published: 2022-12-28 · updated 2026-06-17
Weakness: CWE-669

Description

Elrond-GO is a go implementation for the Elrond Network protocol. Versions prior to 1.3.50 are subject to a processing issue where 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. There are no known workarounds at this time. This issue has been patched in version 1.3.50.

Affected products

ElrondNetwork elrond-go: before 1.3.50 — fixed in 1.3.50

How to fix

Upgrade to a fixed version: ElrondNetwork elrond-go 1.3.50. Check the vendor advisory for mitigations.

References

Get alerted when CVE-2022-46173 or the next vulnerability affects your stack