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

中 6.5CVE-2022-46173 · GHSA-p228-4mrh-ww7r · GO-2022-1200 · 28/12/2022 公開 · 17/06/2026 更新

要点

CVE-2022-46173 は github.com/ElrondNetwork/elrond-go, elrond go (elrond) に影響する深刻度「中」 (CVSS 6.5) の脆弱性です。
今後30日間に悪用される確率（EPSS）：0.79%（全脆弱性の 56.3% より高い）。
対処：1.3.50 以降に更新してください。

パッケージ	影響を受けるバージョン	修正済みバージョン
github.com/ElrondNetwork/elrond-go Go	`< 1.3.50`	`1.3.50`
elrond go elrond	`< 1.3.50`	`1.3.50`

概要

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:

Open an issue in elrond-go main repo

NVD の説明

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.