CVE-2024-34360
Assigner: GitHub_M
Published: 2024-05-10T15:50:05.379Z
State: PUBLISHED
title: Previous ATX is not checked to be the newest valid ATX by Smesher when validating incoming ATX
problemTypes: descriptions: cweId: CWE-754
description: CWE-754: Improper Check for Unusual or Exceptional Conditions
type: CWE
metrics: cvssV3_1: attackComplexity: LOW
attackVector: NETWORK
availabilityImpact: NONE
baseScore: 8.2
baseSeverity: HIGH
confidentialityImpact: HIGH
integrityImpact: LOW
privilegesRequired: NONE
scope: UNCHANGED
userInteraction: NONE
vectorString: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
version: 3.1
affected: vendor: spacemeshos
product: go-spacemesh
versions: version: < 1.5.2-hotfix1
status: affected
descriptions: value: go-spacemesh is a Go implementation of the Spacemesh protocol full node. Nodes can publish activations transactions (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. This vulnerability is fixed in go-spacemesh 1.5.2-hotfix1 and Spacemesh API 1.37.1.
source: advisory: GHSA-jcqq-g64v-gcm7
discovery: UNKNOWN