# CVE-2021-41228: Code injection in `saved_model_cli` > Attackers can execute arbitrary code via the saved_model_cli tool due to unsafe eval usage, requiring manual execution of the CLI. - **Severity:** High 7.5 (`CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** An administrator - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 5 Nov 2021 - **Updated:** 4 Aug 2024 - **Also known as:** BIT-tensorflow-2021-41228, GHSA-3rcw-9p9x-582v, PYSEC-2021-420, PYSEC-2021-637, PYSEC-2021-835 ## What is CVE-2021-41228? CVE-2021-41228 is a high-severity code injection vulnerability in Google Tensorflow, published on 5 Nov 2021. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description TensorFlow is an open source platform for machine learning. In affected versions TensorFlow's `saved_model_cli` tool is vulnerable to a code injection as it calls `eval` on user supplied strings. This can be used by attackers to run arbitrary code on the plaform where the CLI tool runs. However, given that the tool is always run manually, the impact of this is not severe. We have patched this by adding a `safe` flag which defaults to `True` and an explicit warning for users. The fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range. Weakness: CWE-94 (Improper Control of Generation of Code), CWE-78 (Improper Neutralization of Special Elements used in an OS Command) ## Which versions are affected by CVE-2021-41228? 22 open source packages ship an affected version, including tensorflow, tensorflow-cpu and tensorflow-gpu. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `tensorflow` | Bitnami | From 2.4.0 | 2.4.4, 2.5.2, 2.6.1 | | `tensorflow` | PyPI | All versions | 2.4.4, 2.5.2, 2.6.1, 2.7.0 | | `tensorflow` | PyPI | All versions | 2.4.4 | | `tensorflow` | PyPI | All versions | 2.4.4 | | `tensorflow` | PyPI | From 2.5.0 | 2.5.2 | | `tensorflow` | PyPI | From 2.5.0 | 2.5.2 | | `tensorflow` | PyPI | From 2.6.0 | 2.6.1 | | `tensorflow` | PyPI | From 2.6.0 | 2.6.1 | | `tensorflow-cpu` | PyPI | All versions | 2.4.4, 2.5.2, 2.6.1, 2.7.0 | | `tensorflow-cpu` | PyPI | All versions | 2.4.4 | | `tensorflow-cpu` | PyPI | All versions | 2.4.4 | | `tensorflow-cpu` | PyPI | From 2.5.0 | 2.5.2 | | `tensorflow-cpu` | PyPI | From 2.5.0 | 2.5.2 | | `tensorflow-cpu` | PyPI | From 2.6.0 | 2.6.1 | | `tensorflow-cpu` | PyPI | From 2.6.0 | 2.6.1 | | `tensorflow-gpu` | PyPI | All versions | 2.4.4, 2.5.2, 2.6.1, 2.7.0 | | `tensorflow-gpu` | PyPI | All versions | 2.4.4 | | `tensorflow-gpu` | PyPI | All versions | 2.4.4 | | `tensorflow-gpu` | PyPI | From 2.5.0 | 2.5.2 | | `tensorflow-gpu` | PyPI | From 2.5.0 | 2.5.2 | | `tensorflow-gpu` | PyPI | From 2.6.0 | 2.6.1 | | `tensorflow-gpu` | PyPI | From 2.6.0 | 2.6.1 | Products: Google Tensorflow. ## How do I fix CVE-2021-41228? Upgrade tensorflow to a fixed version for your release line: 2.4.4, 2.5.2, 2.6.1 or 2.7.0. ## Is CVE-2021-41228 being exploited? There is no known exploitation of CVE-2021-41228 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-2021-35958](https://insights.sbomify.com/CVE-2021-35958/): Path traversal in n/a (critical 9.1) - [CVE-2020-15202](https://insights.sbomify.com/CVE-2020-15202/): Integer truncation in Shard API usage (critical 9.0) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2021-41228 and fix it if it is affected. What it is: CVE-2021-41228 is a high-severity code injection vulnerability in Google Tensorflow, published on 5 Nov 2021. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2021-41228 in the wild and no public exploit code. Affected packages and fixed versions: - tensorflow (Bitnami): affected from 2.4.0; fixed in 2.4.4, 2.5.2, 2.6.1 - tensorflow (PyPI): affected all versions; fixed in 2.4.4, 2.5.2, 2.6.1, 2.7.0 - tensorflow (PyPI): affected all versions; fixed in 2.4.4 - tensorflow (PyPI): affected all versions; fixed in 2.4.4 - tensorflow (PyPI): affected from 2.5.0; fixed in 2.5.2 - tensorflow (PyPI): affected from 2.5.0; fixed in 2.5.2 - tensorflow (PyPI): affected from 2.6.0; fixed in 2.6.1 - tensorflow (PyPI): affected from 2.6.0; fixed in 2.6.1 - tensorflow-cpu (PyPI): affected all versions; fixed in 2.4.4, 2.5.2, 2.6.1, 2.7.0 - tensorflow-cpu (PyPI): affected all versions; fixed in 2.4.4 - tensorflow-cpu (PyPI): affected all versions; fixed in 2.4.4 - tensorflow-cpu (PyPI): affected from 2.5.0; fixed in 2.5.2 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-41228/ (Markdown: https://insights.sbomify.com/CVE-2021-41228/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2021-41228 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-41228 - OSV: https://osv.dev/vulnerability/CVE-2021-41228 --- From sbomify Insights: https://insights.sbomify.com/CVE-2021-41228/ Summaries are generated and may contain mistakes; the official description above is the record.