# CVE-2024-34360: Previous ATX is not checked to be the newest valid ATX by Smesher when validating incoming ATX

> Attackers can exploit incorrect ATX validation to unfairly earn rewards by holding PoST data for less than one epoch.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 May 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-jcqq-g64v-gcm7, GO-2024-2831

## What is CVE-2024-34360?

CVE-2024-34360 is a high-severity vulnerability in spacemeshos go-spacemesh, published on 10 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-754 (Improper Check for Unusual or Exceptional Conditions)

## Which versions are affected by CVE-2024-34360?

6 open source packages ship an affected version, including github.com/spacemeshos/go-spacemesh, github.com/spacemeshos/api and github.com/spacemeshos/api/release/go.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/spacemeshos/go-spacemesh` | Go | All versions | 1.5.2-hotfix1 |
| `github.com/spacemeshos/go-spacemesh` | Go | All versions | 1.5.2-hotfix1 |
| `github.com/spacemeshos/go-spacemesh` | Go | All versions | 1.5.2-hotfix1 |
| `github.com/spacemeshos/api` | Go | All versions | 1.37.1 |
| `github.com/spacemeshos/api` | Go | All versions | 1.37.1 |
| `github.com/spacemeshos/api/release/go` | Go | All versions | 1.37.1 |

## How do I fix CVE-2024-34360?

Upgrade github.com/spacemeshos/go-spacemesh to 1.5.2-hotfix1 or later.

## Is CVE-2024-34360 being exploited?

There is no known exploitation of CVE-2024-34360 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-34360 and fix it if it is affected.

What it is: CVE-2024-34360 is a high-severity vulnerability in spacemeshos go-spacemesh, published on 10 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-34360 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/spacemeshos/go-spacemesh (Go): affected all versions; fixed in 1.5.2-hotfix1
- github.com/spacemeshos/go-spacemesh (Go): affected all versions; fixed in 1.5.2-hotfix1
- github.com/spacemeshos/go-spacemesh (Go): affected all versions; fixed in 1.5.2-hotfix1
- github.com/spacemeshos/api (Go): affected all versions; fixed in 1.37.1
- github.com/spacemeshos/api (Go): affected all versions; fixed in 1.37.1
- github.com/spacemeshos/api/release/go (Go): affected all versions; fixed in 1.37.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-34360/ (Markdown: https://insights.sbomify.com/CVE-2024-34360/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-34360
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-34360
- OSV: https://osv.dev/vulnerability/CVE-2024-34360

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-34360/
Summaries are generated and may contain mistakes; the official description above is the record.