# CVE-2020-10937: Access Restriction Bypass in go-ipfs

> Attackers can eclipse target nodes by poisoning routing tables via Sybil attacks, requiring an upgrade to mitigate.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 2 Nov 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-r23h-3jmw-q7hr, GO-2024-2779

## What is CVE-2020-10937?

CVE-2020-10937 is a high-severity vulnerability in n/a, published on 2 Nov 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in IPFS (aka go-ipfs) 0.4.23. An attacker can generate ephemeral identities (Sybils) and leverage the IPFS connection management reputation system to poison other nodes' routing tables, eclipsing the nodes that are the target of the attack from the rest of the network. Later versions, in particular go-ipfs 0.7, mitigate this.

## Which versions are affected by CVE-2020-10937?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/ipfs/go-ipfs` | Go | All versions | 0.7.0 |
| `github.com/ipfs/go-ipfs` | Go | All versions | 0.7.0 |
| `github.com/ipfs/go-ipfs` | Go | All versions | 0.7.0 |

Products: Protocol Ipfs.

## How do I fix CVE-2020-10937?

Upgrade github.com/ipfs/go-ipfs to 0.7.0 or later.

## Is CVE-2020-10937 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-10937 and fix it if it is affected.

What it is: CVE-2020-10937 is a high-severity vulnerability in n/a, published on 2 Nov 2020. 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-2020-10937 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/ipfs/go-ipfs (Go): affected all versions; fixed in 0.7.0
- github.com/ipfs/go-ipfs (Go): affected all versions; fixed in 0.7.0
- github.com/ipfs/go-ipfs (Go): affected all versions; fixed in 0.7.0

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

## Sources

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

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