CVE-2021-37646 Bad alloc in `StringNGrams` caused by integer conversion in TensorFlow

Medium 5.5 Published Updated

An attacker can cause a denial of service in TensorFlow by supplying negative ngram widths, triggering an integer overflow and bad allocation.

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

CVE-2021-37646 is a medium-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 implementation of `tf.raw_ops.StringNGrams` is vulnerable to an integer overflow issue caused by converting a signed integer value to an unsigned one and then allocating memory based on this value. The [implementation](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/string_ngrams_op.cc#L184) calls `reserve` on a `tstring` with a value that sometimes can be negative if user supplies negative `ngram_widths`. The `reserve` method calls `TF_TString_Reserve` which has an `unsigned long` argument for the size of the buffer. Hence, the implicit conversion transforms the negative value to a large integer. We have patched the issue in GitHub commit c283e542a3f422420cfdb332414543b62fc4e4a5. 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-681

Which versions are affected by CVE-2021-37646?

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

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

Is CVE-2021-37646 being exploited?

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

All Google Tensorflow vulnerabilities

Sources

Also known as BIT-tensorflow-2021-37646, GHSA-h6jh-7gv5-28vg, PYSEC-2021-268, PYSEC-2021-559, PYSEC-2021-757.

Is CVE-2021-37646 in your software?

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

Check your SBOMs for free