CVE-2021-37665 Incomplete validation in MKL requantization in TensorFlow

High 7.8 Published Updated

Attackers can trigger undefined behavior via null pointer dereference or out-of-bounds heap access in TensorFlow's MKL requantization kernels.

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-37665?

CVE-2021-37665 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 due to incomplete validation in MKL implementation of requantization, an attacker can trigger undefined behavior via binding a reference to a null pointer or can access data outside the bounds of heap allocated arrays. The [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/mkl/mkl_requantization_range_per_channel_op.cc) does not validate the dimensions of the `input` tensor. A similar issue occurs in `MklRequantizePerChannelOp`. The [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/mkl/mkl_requantize_per_channel_op.cc) does not perform full validation for all the input arguments. We have patched the issue in GitHub commit 9e62869465573cb2d9b5053f1fa02a81fce21d69 and in the Github commit 203214568f5bc237603dbab6e1fd389f1572f5c9. 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-20

Which versions are affected by CVE-2021-37665?

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-37665?

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

Is CVE-2021-37665 being exploited?

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

All Google Tensorflow vulnerabilities

Sources

Also known as BIT-tensorflow-2021-37665, GHSA-v82p-hv3v-p6qp, PYSEC-2021-287, PYSEC-2021-578, PYSEC-2021-776.

Is CVE-2021-37665 in your software?

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

Check your SBOMs for free