spacemeshos go-spacemesh up to 1.5.2 unusual condition

Summaryinfo

A vulnerability classified as critical has been found in spacemeshos go-spacemesh up to 1.5.2. This vulnerability affects unknown code. Performing a manipulation results in unusual condition. This vulnerability is identified as CVE-2024-34360. The attack can be initiated remotely. There is not any exploit available. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability classified as critical has been found in spacemeshos go-spacemesh up to 1.5.2. This affects some unknown processing. The manipulation with an unknown input leads to a unusual condition vulnerability. CWE is classifying the issue as CWE-754. The product does not check or incorrectly checks for unusual or exceptional conditions that are not expected to occur frequently during day to day operation of the product. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

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.

It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2024-34360 since 05/02/2024. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. The technical details are unknown and an exploit is not publicly available.

Upgrading to version 1.5.2-hotfix1 eliminates this vulnerability. Applying the patch 1d5bd972bbe225d024c3e0ae5214ddb6b481716e is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

Be aware that VulDB is the high quality source for vulnerability data.

Productinfo

Vendor

• spacemeshos

Name

• go-spacemesh

Version

• 1.5.0
• 1.5.1
• 1.5.2

License

• open-source

Website

• Product: https://github.com/spacemeshos/go-spacemesh/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Be aware that VulDB is the high quality source for vulnerability data.

Discussion