Skip to content

mx-chain-go does not treat invalid transaction with wrong username correctly

High severity GitHub Reviewed Published May 29, 2023 in multiversx/mx-chain-go • Updated Nov 4, 2023

Package

gomod github.com/multiversx/mx-chain-go (Go)

Affected versions

< 1.4.16

Patched versions

1.4.16

Description

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

References

@iulianpascalau iulianpascalau published to multiversx/mx-chain-go May 29, 2023
Published by the National Vulnerability Database May 31, 2023
Published to the GitHub Advisory Database Jun 2, 2023
Reviewed Jun 2, 2023
Last updated Nov 4, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Changed
Confidentiality
None
Integrity
High
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N

EPSS score

0.091%
(40th percentile)

Weaknesses

CVE ID

CVE-2023-33964

GHSA ID

GHSA-7xpv-4pm9-xch2

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.