# CVE-2020-26283: Control character injection in console output

> Attackers can inject control characters into console output to hide input, potentially tricking users into malicious actions.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 24 Mar 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-r4gv-vj59-cccm, GO-2022-0873

## What is CVE-2020-26283?

CVE-2020-26283 is a medium-severity vulnerability in go-ipfs, published on 24 Mar 2021. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

go-ipfs is an open-source golang implementation of IPFS which is a global, versioned, peer-to-peer filesystem. In go-ipfs before version 0.8.0, control characters are not escaped from console output. This can result in hiding input from the user which could result in the user taking an unknown, malicious action. This is fixed in version 0.8.0.

Weakness: CWE-116 (Improper Encoding or Escaping of Output)

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

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.8.0 |
| `github.com/ipfs/go-ipfs` | Go | All versions | 0.8.0 |
| `github.com/ipfs/go-ipfs` | Go | All versions | 0.8.0 |

Products: Protocol Go-Ipfs.

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

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

## Is CVE-2020-26283 being exploited?

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

## Other vulnerabilities in go-ipfs

- [CVE-2020-26279](https://insights.sbomify.com/CVE-2020-26279/): Path traversal (high 7.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-26283 is a medium-severity vulnerability in go-ipfs, published on 24 Mar 2021. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2020-26283 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.8.0
- github.com/ipfs/go-ipfs (Go): affected all versions; fixed in 0.8.0
- github.com/ipfs/go-ipfs (Go): affected all versions; fixed in 0.8.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-26283/ (Markdown: https://insights.sbomify.com/CVE-2020-26283/index.md)
```

## Sources

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

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