CVE-2023-33964: mx-chain-go does not treat invalid transaction with wrong username correctly

Published May 31, 2023
·
Updated

Impact Metachain cannot process a cross-shard miniblock. An invalid transaction with the wrong username on metachain is not treated correctly on the metachain transaction processor. This is strictly a processing issue that could have happened on MultiversX chain. If an error like this had occurred, the metachain would have stopped notarizing blocks from the shard chains. The resuming of notarization is possible only after applying a patched binary version. Patches Introduce processIfTxErrorCrossShard for metachain transaction processor.

Workarounds No

References No

Other sources

mx-chain-go is an implementation of the MultiversX blockchain protocol written in the Go language. Metachain cannot process a cross-shard miniblock. Prior to version 1.4.16, an invalid transaction with the wrong username on metachain is not treated correctly on the metachain transaction processor. This is strictly a processing issue that could have happened on MultiversX chain. If an error like this had occurred, the metachain would have stopped notarizing blocks from the shard chains. The resuming of notarization is possible only after applying a patched binary version. A patch in version 1.4.16 introduces processIfTxErrorCrossShard for the metachain transaction processor. There are no known workarounds for this issue.

Affected Software

2 affected componentsFixes available
go/github.com/multiversx/mx-chain-go<1.4.16
1.4.16
MultiversX Mx-chain-go Go<1.4.16

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade go/github.com/multiversx/mx-chain-go to a version that resolves this vulnerability.

    Fixed in 1.4.16
  2. Upgrade

    Upgrade mx-chain-go to a version that resolves this vulnerability.

    Fixed in 1.4.16
  3. Compensating control

    If the notarization has stopped due to an invalid metachain transaction with the wrong username (cross-shard error case), resume notarization only after applying the patched binary version.

Event History

May 31, 2023
CVE Published
via MITRE·05:07 PM
Data Sourced
via MITRE·05:07 PM
DescriptionSeverityWeakness
Data Sourced
06:15 PM
Description
Data Sourced
via NVD·06:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Jun 2, 2023
Advisory Published
07:41 PM

Frequently Asked Questions

1

What is the severity of CVE-2023-33964?

The severity of CVE-2023-33964 is not explicitly classified, but it is related to a processing issue on the Metachain.

2

How do I fix CVE-2023-33964?

To fix CVE-2023-33964, update the affected MultiversX Mx-chain-go package to version 1.4.16 or later.

3

What are the potential consequences of CVE-2023-33964?

CVE-2023-33964 could result in improper processing of cross-shard miniblocks, leading to transaction errors.

4

Which version of MultiversX Mx-chain-go is affected by CVE-2023-33964?

CVE-2023-33964 affects all versions of the MultiversX Mx-chain-go package prior to 1.4.16.

5

Is CVE-2023-33964 specific to any platform?

Yes, CVE-2023-33964 is specific to the Metachain and could impact applications running on the MultiversX chain.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203