Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.
Open advisories
3 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.
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
Recommended action: Upgrade to 1.3.50 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
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/asyncESDTtest.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: Open an issue in elrond-go (http://github.com/ElrondNetwork/elrond-go/issues)
Recommended action: Upgrade to 1.3.35 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
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]](https://github.com/ElrondNetwork/elrond-go/blob/8e402fa6d7e91e779980122d3798b2bf50892945/integrationTests/vm/txsFee/asyncESDTtest.go#L402) For more information If you have any questions or comments about this advisory: Open an issue in elrond-go (http://github.com/ElrondNetwork/elrond-go/issues)
Recommended action: Upgrade to 1.3.34 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.