# CVE-2022-37450: Go Ethereum allows attackers to use manipulation of time-difference values to achieve replacement of main-chain blocks

> Attackers can manipulate time-difference values to replace main-chain blocks and increase mining rewards, affecting Ethereum network integrity.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/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:** 5 Aug 2022
- **Updated:** 3 Aug 2024
- **Also known as:** CLEANSTART-2024-DV35660, GHSA-rqmg-hrg4-fm69

## What is CVE-2022-37450?

CVE-2022-37450 is a medium-severity vulnerability in n/a, published on 5 Aug 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Go Ethereum (aka geth) through 1.10.21 allows attackers to increase rewards by mining blocks in certain situations, and using a manipulation of time-difference values to achieve replacement of main-chain blocks, aka Riskless Uncle Making (RUM), as exploited in the wild in 2020 through 2022.

## Which versions are affected by CVE-2022-37450?

2 open source packages ship an affected version, including github.com/ethereum/go-ethereum. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/ethereum/go-ethereum` | Go | All versions to 1.10.21 | None |
| `github.com/ethereum/go-ethereum` | Go | All versions to 1.10.21 | None |

Products: Ethereum Go Ethereum.

## How do I fix CVE-2022-37450?

Upgrade to a fixed version.

## Is CVE-2022-37450 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2026-26314](https://insights.sbomify.com/CVE-2026-26314/): Go Ethereum affected by DoS via malicious p2p message (high 8.7)
- [CVE-2023-42319](https://insights.sbomify.com/CVE-2023-42319/): go-ethereum vulnerable to denial of service via crafted GraphQL query (high 7.5)
- [CVE-2023-40591](https://insights.sbomify.com/CVE-2023-40591/): Denial of service via malicious p2p message in go-ethereum (high 7.5)
- [CVE-2021-42219](https://insights.sbomify.com/CVE-2021-42219/): Denial of service in go-ethereum (high 7.5)
- [CVE-2022-23327](https://insights.sbomify.com/CVE-2022-23327/): Denial of Service in Go-Ethereum (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-37450 and fix it if it is affected.

What it is: CVE-2022-37450 is a medium-severity vulnerability in n/a, published on 5 Aug 2022. 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-2022-37450 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/ethereum/go-ethereum (Go): affected all versions up to 1.10.21; no fix listed
- github.com/ethereum/go-ethereum (Go): affected all versions up to 1.10.21; no fix listed

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-2022-37450/ (Markdown: https://insights.sbomify.com/CVE-2022-37450/index.md)
```

## Sources

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

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