# CVE-2021-41394: Supply chain in n/a

> Attackers can alter build artifacts in Teleport, potentially leading to code execution or security bypasses in deployed environments.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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:** 18 Sep 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-8pmf-jxj3-wvvp

## What is CVE-2021-41394?

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

### Official description

Teleport before 4.4.11, 5.x before 5.2.4, 6.x before 6.2.12, and 7.x before 7.1.1 allows alteration of build artifacts in some situations.

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

It affects 1 product.


Products: Goteleport Teleport.

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

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

## Is CVE-2021-41394 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-41393](https://insights.sbomify.com/CVE-2021-41393/): Security feature bypass in n/a (critical 9.8)
- [CVE-2022-36633](https://insights.sbomify.com/CVE-2022-36633/): Improper token validation leading to code execution in Teleport (high 8.8)
- [CVE-2022-38599](https://insights.sbomify.com/CVE-2022-38599/): Information disclosure in n/a (medium 6.5)
- [CVE-2021-41395](https://insights.sbomify.com/CVE-2021-41395/): Other in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-41394 is a medium-severity vulnerability in n/a, published on 18 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-41394 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-41394/ (Markdown: https://insights.sbomify.com/CVE-2021-41394/index.md)
```

## Sources

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

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