# CVE-2021-29539: Segfault in tf.raw_ops.ImmutableConst > Calling tf.raw_ops.ImmutableConst with specific dtypes causes a segmentation fault, leading to denial of service in applications using TensorFlow. - **Severity:** Low 2.5 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 14 May 2021 - **Updated:** 3 Aug 2024 - **Also known as:** BIT-tensorflow-2021-29539, GHSA-g4h2-gqm3-c9wq, PYSEC-2021-176, PYSEC-2021-467, PYSEC-2021-665 ## What is CVE-2021-29539? CVE-2021-29539 is a low-severity vulnerability in Google Tensorflow, published on 14 May 2021. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description TensorFlow is an end-to-end open source platform for machine learning. Calling `tf.raw_ops.ImmutableConst`(https://www.tensorflow.org/api_docs/python/tf/raw_ops/ImmutableConst) with a `dtype` of `tf.resource` or `tf.variant` results in a segfault in the implementation as code assumes that the tensor contents are pure scalars. We have patched the issue in 4f663d4b8f0bec1b48da6fa091a7d29609980fa4 and will release TensorFlow 2.5.0 containing the patch. TensorFlow nightly packages after this commit will also have the issue resolved. If using `tf.raw_ops.ImmutableConst` in code, you can prevent the segfault by inserting a filter for the `dtype` argument. Weakness: CWE-681 (Incorrect Conversion between Numeric Types) ## Which versions are affected by CVE-2021-29539? 28 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 | All versions | 2.1.4, 2.2.3, 2.3.3, 2.4.2 | | `tensorflow` | PyPI | All versions | 2.2.0rc0, 2.3.0rc0, 2.3.4, 2.4.3 | | `tensorflow` | PyPI | All versions | 2.1.4 | | `tensorflow` | PyPI | All versions | 2.1.4 | | `tensorflow` | PyPI | From 2.2.0 | 2.2.3 | | `tensorflow` | PyPI | From 2.2.0 | 2.2.3 | | `tensorflow` | PyPI | From 2.3.0 | 2.3.3 | | `tensorflow` | PyPI | From 2.3.0 | 2.3.3 | | `tensorflow` | PyPI | From 2.4.0 | 2.4.2 | | `tensorflow` | PyPI | From 2.4.0 | 2.4.2 | | `tensorflow-cpu` | PyPI | All versions | 2.2.0rc0, 2.3.0rc0, 2.3.4, 2.4.3 | | `tensorflow-cpu` | PyPI | All versions | 2.1.4 | | `tensorflow-cpu` | PyPI | All versions | 2.1.4 | | `tensorflow-cpu` | PyPI | From 2.2.0 | 2.2.3 | | `tensorflow-cpu` | PyPI | From 2.2.0 | 2.2.3 | | `tensorflow-cpu` | PyPI | From 2.3.0 | 2.3.3 | | `tensorflow-cpu` | PyPI | From 2.3.0 | 2.3.3 | | `tensorflow-cpu` | PyPI | From 2.4.0 | 2.4.2 | | `tensorflow-cpu` | PyPI | From 2.4.0 | 2.4.2 | | `tensorflow-gpu` | PyPI | All versions | 2.2.0rc0, 2.3.0rc0, 2.3.4, 2.4.3 | | `tensorflow-gpu` | PyPI | All versions | 2.1.4 | | `tensorflow-gpu` | PyPI | All versions | 2.1.4 | | `tensorflow-gpu` | PyPI | From 2.2.0 | 2.2.3 | | `tensorflow-gpu` | PyPI | From 2.2.0 | 2.2.3 | | `tensorflow-gpu` | PyPI | From 2.3.0 | 2.3.3 | | `tensorflow-gpu` | PyPI | From 2.3.0 | 2.3.3 | | `tensorflow-gpu` | PyPI | From 2.4.0 | 2.4.2 | | `tensorflow-gpu` | PyPI | From 2.4.0 | 2.4.2 | Products: Google Tensorflow. ## How do I fix CVE-2021-29539? Upgrade tensorflow to a fixed version for your release line: 2.1.4, 2.2.3, 2.3.3 or 2.4.2. ## Is CVE-2021-29539 being exploited? There is no known exploitation of CVE-2021-29539 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-29539 and fix it if it is affected. What it is: CVE-2021-29539 is a low-severity vulnerability in Google Tensorflow, published on 14 May 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-29539 in the wild and no public exploit code. Affected packages and fixed versions: - tensorflow (Bitnami): affected all versions; fixed in 2.1.4, 2.2.3, 2.3.3, 2.4.2 - tensorflow (PyPI): affected all versions; fixed in 2.2.0rc0, 2.3.0rc0, 2.3.4, 2.4.3 - tensorflow (PyPI): affected all versions; fixed in 2.1.4 - tensorflow (PyPI): affected all versions; fixed in 2.1.4 - tensorflow (PyPI): affected from 2.2.0; fixed in 2.2.3 - tensorflow (PyPI): affected from 2.2.0; fixed in 2.2.3 - tensorflow (PyPI): affected from 2.3.0; fixed in 2.3.3 - tensorflow (PyPI): affected from 2.3.0; fixed in 2.3.3 - tensorflow (PyPI): affected from 2.4.0; fixed in 2.4.2 - tensorflow (PyPI): affected from 2.4.0; fixed in 2.4.2 - tensorflow-cpu (PyPI): affected all versions; fixed in 2.2.0rc0, 2.3.0rc0, 2.3.4, 2.4.3 - tensorflow-cpu (PyPI): affected all versions; fixed in 2.1.4 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-29539/ (Markdown: https://insights.sbomify.com/CVE-2021-29539/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2021-29539 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-29539 - OSV: https://osv.dev/vulnerability/CVE-2021-29539 --- From sbomify Insights: https://insights.sbomify.com/CVE-2021-29539/ Summaries are generated and may contain mistakes; the official description above is the record.