CVE-2020-10937 json
Access Restriction Bypass in go-ipfs
published 6y ago modified 4mo ago also GHSA-r23h-3jmw-q7hr , GO-2024-2779 , EUVD-2024-1286
- cvss
- 7.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.2%
- EPSS 1.2% chance of exploitation in 30 days, percentile 67%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- go github.com/ipfs/go-ipfs 0.7.0
Is CVE-2020-10937 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
1.16% chance of exploitation in the next 30 days, higher than 67% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:N/A:P |
| GitHub | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/ipfs/go-ipfs | <0.7.0 |
0.7.0 |
Classification
- Weakness
-
- CWE-284 Improper Access Control
References
-
blog.ipfs.io
/2020-10-30-dht-hardening/
vendor-advisory
-
graz.pure.elsevier.com
/en/publications/total-eclipse-of-the-heart-disrupting-the-interplanetary-file-sys
web, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2020-10937
advisory
-
blog.ipfs.io
/2020-10-30-dht-hardening
web
-
github.com
/advisories/GHSA-r23h-3jmw-q7hr
advisory
Sources
- CVE List CVE-2020-10937
- GitHub Advisory GHSA-r23h-3jmw-q7hr
- NVD CVE-2020-10937
- OSV GO-2024-2779
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.