# CVE-2021-35958: Path traversal in n/a

> Attackers can overwrite arbitrary files via crafted archives in TensorFlow's get_file utility, though the vendor deems this out of scope for untrusted input.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Jun 2021
- **Updated:** 4 Aug 2024
- **Also known as:** BIT-tensorflow-2021-35958, GHSA-4cm9-63x5-55wm

## What is CVE-2021-35958?

CVE-2021-35958 is a critical path traversal vulnerability in Google Tensorflow, published on 30 Jun 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

TensorFlow through 2.5.0 allows attackers to overwrite arbitrary files via a crafted archive when tf.keras.utils.get_file is used with extract=True. NOTE: the vendor's position is that tf.keras.utils.get_file is not intended for untrusted archives

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

1 open source package ship an affected version, including tensorflow. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `tensorflow` | Bitnami | All versions | 2.5.1 |

Products: Google Tensorflow.

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

Upgrade tensorflow to 2.5.1 or later.

## Is CVE-2021-35958 being exploited?

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

## Other vulnerabilities in Google Tensorflow

- [CVE-2023-25668](https://insights.sbomify.com/CVE-2023-25668/): TensorFlow vulnerable to heap out-of-buffer read in the QuantizeAndDequantize operation (critical 9.8)
- [CVE-2018-7575](https://insights.sbomify.com/CVE-2018-7575/): Integer Overflow or Wraparound in Google TensorFlow (critical 9.8)
- [CVE-2021-37678](https://insights.sbomify.com/CVE-2021-37678/): Arbitrary code execution due to YAML deserialization (critical 9.3)
- [CVE-2020-15202](https://insights.sbomify.com/CVE-2020-15202/): Integer truncation in Shard API usage (critical 9.0)
- [CVE-2020-15205](https://insights.sbomify.com/CVE-2020-15205/): Data leak in Tensorflow (critical 9.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-35958 is a critical path traversal vulnerability in Google Tensorflow, published on 30 Jun 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-35958 in the wild and no public exploit code.

Affected packages and fixed versions:
- tensorflow (Bitnami): affected all versions; fixed in 2.5.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-2021-35958/ (Markdown: https://insights.sbomify.com/CVE-2021-35958/index.md)
```

## Sources

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

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