High, CVSS 8.2GoPublished
Previous ATX is not checked to be the newest valid ATX by Smesher when validating incoming ATX
CVE-2024-34360 · GHSA-jcqq-g64v-gcm7
- Affected
- Go github.com/spacemeshos/go-spacemesh < 1.5.2-hotfix1
- Fixed in
- 1.5.2-hotfix1· Vendor fix available
- Issue
- Impact Nodes can publish ATXs which reference the incorrect previous ATX of the Smesher that created the ATX. ATXs are expected to form a single chain from the newest to the first ATX ever published by an identity. Allowing Smeshers to reference an earlier (but not the latest) ATX as previous breaks this protocol rule and can serve as an attack vector where Nodes are rewarded for holding their PoST data for less than one epoch but still being eligible for rewards. Patches - API needs to be extended to be able to fetch events from a node that dected malicious behavior of this regard by the node - go-spacemesh needs to be patched to a) not allow publishing these ATXs any more and b) create malfeasance proofs for identities that published invalid ATXs in the past. Workarounds n/a References Spacemesh protocol whitepaper: https://spacemesh.io/blog/spacemesh-white-paper-1/, specifically sections 4.4.2 ("ATX Contents") and 4.4.3 ("ATX validity")
Recommended action: Upgrade to 1.5.2-hotfix1 (pre-release) or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.