Skip to content

Path traversal in github.com/ipfs/go-ipfs

High severity GitHub Reviewed Published Mar 24, 2021 in ipfs/kubo • Updated Jan 9, 2023

Package

gomod github.com/ipfs/go-ipfs (Go)

Affected versions

< 0.8.0

Patched versions

0.8.0

Description

Impact

It is currently possible for path traversal to occur with DAGs containing relative paths during retrieval. This can cause files to be overwritten, or written to incorrect output directories. The issue can only occur when ipfs get is done on an affected DAG.

  1. The only affected command is ipfs get.
  2. The gateway is not affected.

Patches

Traversal fix patched in whyrusleeping/tar-utils@20a6137
tar-utils patch applied to go-ipfs via ipfs/kubo@b7ddba7

Workarounds

Upgrade to go-ipfs 0.8 or later.

References

Binaries for the patched versions of go-ipfs are available on the IPFS distributions site, https://dist.ipfs.io/go-ipfs

For more information

If you have any questions or comments about this advisory:

References

@jacobheun jacobheun published to ipfs/kubo Mar 24, 2021
Reviewed May 21, 2021
Published to the GitHub Advisory Database Jun 23, 2021
Last updated Jan 9, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
Low
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:N

EPSS score

0.093%
(41st percentile)

Weaknesses

CVE ID

CVE-2020-26279

GHSA ID

GHSA-27pv-q55r-222g

Source code

No known source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.