# CVE-2021-41077: Information disclosure in n/a

> Travis CI exposed secret environment variables to unauthorized actors who forked public repositories during a specific eight-day period.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Sep 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-qg93-hr7r-24gf

## What is CVE-2021-41077?

CVE-2021-41077 is a high-severity vulnerability in n/a, published on 14 Sep 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The activation process in Travis CI, for certain 2021-09-03 through 2021-09-10 builds, causes secret data to have unexpected sharing that is not specified by the customer-controlled .travis.yml file. In particular, the desired behavior (if .travis.yml has been created locally by a customer, and added to git) is for a Travis service to perform builds in a way that prevents public access to customer-specific secret environment data such as signing keys, access credentials, and API tokens. However, during the stated 8-day interval, secret data could be revealed to an unauthorized actor who forked a public repository and printed files during a build process.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2021-41077?

It affects 1 product.


Products: Travis-Ci Travis Ci.

## How do I fix CVE-2021-41077?

No fix has been published for CVE-2021-41077 yet. Limit exposure of the affected software until one is available.

## Is CVE-2021-41077 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-41077 and fix it if it is affected.

What it is: CVE-2021-41077 is a high-severity vulnerability in n/a, published on 14 Sep 2021. 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-2021-41077 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

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

## Sources

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

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