Advisory

GHSA-j494-7x2v-vvvp

Also known as: CVE-2023-34458, GO-2023-1912

Summary

mx-chain-go's relayed transactions always increment nonce

Details

Impact
When executing a relayed transaction, if the inner transaction failed, it would have increased the inner transaction's sender account nonce. This could have contributed to a limited DoS attack on a targeted account. The fix is a breaking change so a new flag RelayedNonceFixEnableEpoch was needed. This was a strict processing issue while validating blocks on a chain.

Patches
v1.4.17 and later versions contain the fix for this issue

Workarounds
there were no workarounds for this issue. The affected account could only wait for the DoS attack to finish as the attack was not free or to attempt to send transactions in a very fast manner so as to compete on the same nonce with the attacker.

References
For the future understanding of this issue, on v1.4.17 and onwards versions, we have this integration test that addresses the issue and tests the fix.
https://github.com/multiversx/mx-chain-go/blob/babdb144f1316ab6176bf3dbd7d4621120414d43/integrationTests/vm/txsFee/relayedMoveBalance_test.go#LL165C14-L165C14

Severity

High Basis: The source's own band: HIGH

Dates

Published
2023-07-13 17:02 UTC
Modified
2024-08-20 20:58 UTC

Affected packages and fixes

github.com/multiversx/mx-chain-go

Go · All systems

Affected

  • introduced 0, fixed 1.4.17 (semver)

Fixed versions

1.4.17

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences