# CVE-2020-11059: Exposure of Sensitive Information to an Unauthorized Actor in AEgir

> AEgir build tool leaks environment variable secrets into published browser bundles, exposing sensitive data to unauthorized actors.

- **Severity:** Critical 9.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 27 May 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-qfcv-5whw-7pcw

## What is CVE-2020-11059?

CVE-2020-11059 is a critical vulnerability in IPFS AEgir, published on 27 May 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

In AEgir greater than or equal to 21.7.0 and less than 21.10.1, aegir publish and aegir build may leak secrets from environment variables in the browser bundle published to npm. This has been fixed in 21.10.1.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

2 open source packages ship an affected version, including aegir. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `aegir` | npm | From 21.7.0 | 21.10.1 |
| `aegir` | npm | From 21.7.0 | 21.10.1 |

Products: Aegir Project Aegir.

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

Upgrade aegir to 21.10.1 or later.

## Is CVE-2020-11059 being exploited?

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

## Other vulnerabilities in IPFS AEgir

- [CVE-2017-16225](https://insights.sbomify.com/CVE-2017-16225/): Github Token Leak in aegir (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-11059 is a critical vulnerability in IPFS AEgir, published on 27 May 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2020-11059 in the wild and no public exploit code.

Affected packages and fixed versions:
- aegir (npm): affected from 21.7.0; fixed in 21.10.1
- aegir (npm): affected from 21.7.0; fixed in 21.10.1

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

## Sources

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

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