CVE-2021-37648 Incorrect validation of `SaveV2` inputs in TensorFlow

High 7.8 Published Updated

An attacker can trigger a null pointer dereference in TensorFlow's SaveV2 operation due to improper input validation, causing a denial of service.

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

What is CVE-2021-37648?

CVE-2021-37648 is a high-severity vulnerability in Google Tensorflow, published on 12 Aug 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. In affected versions the code for `tf.raw_ops.SaveV2` does not properly validate the inputs and an attacker can trigger a null pointer dereference. The [implementation](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/save_restore_v2_ops.cc) uses `ValidateInputs` to check that the input arguments are valid. This validation would have caught the illegal state represented by the reproducer above. However, the validation uses `OP_REQUIRES` which translates to setting the `Status` object of the current `OpKernelContext` to an error status, followed by an empty `return` statement which just terminates the execution of the function it is present in. However, this does not mean that the kernel execution is finalized: instead, execution continues from the next line in `Compute` that follows the call to `ValidateInputs`. This is equivalent to lacking the validation. We have patched the issue in GitHub commit 9728c60e136912a12d99ca56e106b7cce7af5986. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range.

Weakness: CWE-476

Which versions are affected by CVE-2021-37648?

22 open source packages ship an affected version, including tensorflow, tensorflow-cpu and tensorflow-gpu. It affects 1 product.

PackageAffectedFixed in
tensorflow BitnamiFrom 2.3.02.3.4, 2.4.3, 2.5.1
tensorflow PyPIAll versions2.3.4
tensorflow PyPIAll versions2.3.4
tensorflow PyPIFrom 2.3.02.3.4, 2.4.3
tensorflow PyPIFrom 2.4.02.4.3
tensorflow PyPIFrom 2.4.02.4.3
16 more packages
tensorflow PyPIFrom 2.5.02.5.1
tensorflow PyPIFrom 2.5.02.5.1
tensorflow-cpu PyPIAll versions2.3.4
tensorflow-cpu PyPIAll versions2.3.4
tensorflow-cpu PyPIFrom 2.3.02.3.4, 2.4.3
tensorflow-cpu PyPIFrom 2.4.02.4.3
tensorflow-cpu PyPIFrom 2.4.02.4.3
tensorflow-cpu PyPIFrom 2.5.02.5.1
tensorflow-cpu PyPIFrom 2.5.02.5.1
tensorflow-gpu PyPIAll versions2.3.4
tensorflow-gpu PyPIAll versions2.3.4
tensorflow-gpu PyPIFrom 2.3.02.3.4, 2.4.3
tensorflow-gpu PyPIFrom 2.4.02.4.3
tensorflow-gpu PyPIFrom 2.4.02.4.3
tensorflow-gpu PyPIFrom 2.5.02.5.1
tensorflow-gpu PyPIFrom 2.5.02.5.1

Products include Google Tensorflow.

How do I fix CVE-2021-37648?

Upgrade tensorflow to a fixed version for your release line: 2.3.4, 2.4.3 or 2.5.1.

Is CVE-2021-37648 being exploited?

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

All Google Tensorflow vulnerabilities

Sources

Also known as BIT-tensorflow-2021-37648, GHSA-wp77-4gmm-7cq8, PYSEC-2021-270, PYSEC-2021-561, PYSEC-2021-759.

Is CVE-2021-37648 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free