Advisory

GHSA-jcqq-g64v-gcm7

Also known as: CVE-2024-34360, GO-2024-2831

Summary

Previous ATX is not checked to be the newest valid ATX by Smesher when validating incoming ATX

Details

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")

Severity

High Basis: The source's own band: HIGH

Dates

Published
2024-05-10 15:33 UTC
Modified
2026-09-10 03:49 UTC

Affected packages and fixes

github.com/spacemeshos/go-spacemesh

Go · All systems

Affected

  • introduced 0, fixed 1.5.2-hotfix1 (semver)

Fixed versions

1.5.2-hotfix1

Fix

github.com/spacemeshos/api

Go · All systems

Affected

  • introduced 0, fixed 1.37.1 (semver)

Fixed versions

1.37.1

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